# It's the CLI-mb

**URL:** <https://forums.losant.com/t/its-the-cli-mb/2198>\
**Category:** Losant Tips\
**Tags:** cli, losant-cli\
**Created:** [September 17, 2019, 9:07pm UTC](https://forums.losant.com/t/its-the-cli-mb/2198 "2019-09-17T21:07:10Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![JuliaKempf](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/juliakempf/32/2446_2.png) [@JuliaKempf](https://forums.losant.com/u/JuliaKempf)\
**Post date:** [September 17, 2019, 9:07pm UTC](https://forums.losant.com/t/its-the-cli-mb/2198/1 "2019-09-17T21:07:10Z")

</div>

Did you know Losant has a CLI to help you build experiences? That’s right, release the confetti cannons! The Losant CLI is a great tool for a plethora of reasons, and is designed for power users.

The CLI helps with building experiences by letting you manage [Experience Views](https://docs.losant.com/experiences/views/), [Experience Versions](https://docs.losant.com/experiences/versions/), [Data Tables](https://docs.losant.com/data-tables/overview/), and [Files](https://docs.losant.com/applications/files/) in your Applications. With the Losant CLI, not only can these resources be edited in Losant, but they can be modified locally with your favorite IDE and then automatically synced with your Losant application with a script. Though Losant provides [Experience Versioning](https://docs.losant.com/experiences/versions/) already, the CLI’s functionality also provides options for source control and versioning with your preferred code management platform.

![The CLI in action!](https://us1.discourse-cdn.com/flex015/uploads/getstructure/original/2X/8/89f4a41a204ec392d7d02f93063733ddcbc337e3.gif)

You can get started immediately with the Losant CLI by visiting our [documentation](https://docs.losant.com/cli/overview/) or [Github repository](https://github.com/Losant/losant-cli).

Thanks for stopping by our Tuesday Tip, we hope this one rocked. Don’t forget to send us your suggestions and discoveries. ⛏ Keep exploring!  
Julia

---

<div class="post-metadata">

**Author:** ![paul\_wareham](https://avatars.discourse-cdn.com/v4/letter/p/ed8c4c/32.png) [@paul\_wareham](https://forums.losant.com/u/paul_wareham)\
**Post date:** [September 21, 2019, 2:36pm UTC](https://forums.losant.com/t/its-the-cli-mb/2198/2 "2019-09-21T14:36:02Z")

</div>

Just wishing CLI supported workflows 🙂

---

<div class="post-metadata">

**Author:** ![anaptfox](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/anaptfox/32/873_2.png) [@anaptfox](https://forums.losant.com/u/anaptfox)\
**Post date:** [September 21, 2019, 2:37pm UTC](https://forums.losant.com/t/its-the-cli-mb/2198/3 "2019-09-21T14:37:36Z")

</div>

Hi @paul_wareham,

Out of curiosity, what would you do with Workflows from the CLI?

---

<div class="post-metadata">

**Author:** ![paul\_wareham](https://avatars.discourse-cdn.com/v4/letter/p/ed8c4c/32.png) [@paul\_wareham](https://forums.losant.com/u/paul_wareham)\
**Post date:** [September 21, 2019, 2:38pm UTC](https://forums.losant.com/t/its-the-cli-mb/2198/4 "2019-09-21T14:38:54Z")

</div>

I would version control them in git

---

<div class="post-metadata">

**Author:** ![paul\_wareham](https://avatars.discourse-cdn.com/v4/letter/p/ed8c4c/32.png) [@paul\_wareham](https://forums.losant.com/u/paul_wareham)\
**Post date:** [September 21, 2019, 2:39pm UTC](https://forums.losant.com/t/its-the-cli-mb/2198/5 "2019-09-21T14:39:45Z")

</div>

I was curious to know which IDE the Losant folks prefer for editing hbs files locally?

---

<div class="post-metadata">

**Author:** ![anaptfox](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/anaptfox/32/873_2.png) [@anaptfox](https://forums.losant.com/u/anaptfox)\
**Post date:** [September 21, 2019, 2:41pm UTC](https://forums.losant.com/t/its-the-cli-mb/2198/6 "2019-09-21T14:41:51Z")

</div>

Ah I see, Did you know that we support [versioning of workflows](https://docs.losant.com/workflows/versioning/) within the platform? Even for [Experiences](https://docs.losant.com/experiences/versions/) too.

Here, most of use and like [VS Code](https://code.visualstudio.com). 🙂

---

<div class="post-metadata">

**Author:** ![paul\_wareham](https://avatars.discourse-cdn.com/v4/letter/p/ed8c4c/32.png) [@paul\_wareham](https://forums.losant.com/u/paul_wareham)\
**Post date:** [September 21, 2019, 3:34pm UTC](https://forums.losant.com/t/its-the-cli-mb/2198/7 "2019-09-21T15:34:17Z")

</div>

Yes for sure. Aware of the versioning however that makes it non standard from our company’s revision control systems based on git.

---

<div class="post-metadata">

**Author:** ![paul\_wareham](https://avatars.discourse-cdn.com/v4/letter/p/ed8c4c/32.png) [@paul\_wareham](https://forums.losant.com/u/paul_wareham)\
**Post date:** [September 22, 2019, 4:02pm UTC](https://forums.losant.com/t/its-the-cli-mb/2198/8 "2019-09-22T16:02:18Z")

</div>

I should add that one of the more awkward parts of the process is source control for any custom code in Function nodes. Versioning and diff capabilities with git would be useful.

---

<div class="post-metadata">

**Author:** ![JuliaKempf](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/juliakempf/32/2446_2.png) [@JuliaKempf](https://forums.losant.com/u/JuliaKempf)\
**Post date:** [September 23, 2019, 2:07pm UTC](https://forums.losant.com/t/its-the-cli-mb/2198/9 "2019-09-23T14:07:45Z")

</div>

Hi @paul_wareham,

Thanks for the explanation! 😄 I will be sure to add these comments to your feature request to give our engineers some more details.

Thanks again,  
Julia
