With Liteflow, the current ecosystem of MESG has changed, and your application is slightly different, but that’s for the best.

This article is a step-by-step guide on how to migrate your MESG application to Liteflow.

New CLI

Liteflow has a new CLI that is quite similar to the MESG CLI that you can install with:

npm install -g @liteflow/cli

Service migration

Services now rely on a new library @liteflow/service. This library has changed internally, but the API stays the same, so you shouldn't have any issue in your service.

npm remove @mesg/service
npm install @liteflow/service

Replace in the code of your service all require to the @mesg/service with the new one @liteflow/service, and your service is ready to go.

The Liteflow framework

We introduced a new way to organize your applications.

You can now group processes/services in the same directory and run everything with a unique command saving a lot of time and letting you easily test multiple processes and services at the same time.

You can create such an application with:

liteflow init

And run your application with:

liteflow dev

A local development environment will be automatically started and stopped on your local computer. You can now use only one terminal and forget about the daemon commands.

Thanks to the Liteflow framework, you can now more easily create sophisticated applications that rely on multiple processes.

More details on the new Liteflow documentation (https://docs.liteflow.com/).

Deployment of your application

Deploying an application with MESG was complicated and only limited to a public testnet. This process really time-consuming as you had to:

  • Generate an address from a mnemonic
  • Get some tokens from the MESG Testnet faucet β€” WTF is a faucet? 🚰
  • Configure your local engine to connect to the MESG Testnet β€” Good luck with that one... https://github.com/mesg-foundation/networks 🀯
  • Wait to synchronize the testnet β€” Do you have a few days? πŸ₯±
  • Finally, publish your services and processes with the same commands that you used for your development β€” Wait... what? But am I still developing or pushing that in prod? 🀨
  • Wait, not entirely done... All your services and processes are deployed, but good luck remember which one belongs to which application β€” A spreadsheet would do the work πŸ˜…

This flow was really complicated and confusing, especially for developers that have no experience with blockchain. With Liteflow, your deployment is much simpler and way faster:

  • Use the command liteflow deploy β€” The previously first five steps are just one now. πŸ₯³
  • Choose or create the project you want β€” Clear organization of your applications. 🀩
  • Your application is now running on a production environment with free credits β€” In just a few seconds your services and processes are deployed and started. 😍

Bonus: You can manage your application directly through the console at console.liteflow.com.


Feel free to deploy amazing applications on Liteflow.