Deploying

When you deploy your project repository to the Movable Ink platform, most of what happens is server-side. The following happens:

• The contents of your repository are synced to Movable Ink's servers.
• The platform uses the repository name to determine the project's "key"--if the platform already has an existing app with the same key and you have access to that project, it will attempt to update that app, otherwise it will create a new app in the platform.
• The platform examines your package.json file and installs any dependencies.
• The platform executes yarn run build, which takes all of the javascript from your project's app/ directory and compiles it into files in a dist directory.
• The platform pushes the contents of your repository, including the newly created dist/ files, to Movable Ink's asset servers.
• The platform updates the app to use this latest release for any new apps users create. Any existing app instances users have created will continue to use the release that was active at the time the app instances were created.

In order to deploy, you first need to authenticate with the Movable Ink platform. You can do so with:

$ movable login

This will ask you to open a browser window to complete the oAuth-based authentication process with the platform. Once you do so you should see a "Success" message.

To deploy your app, first ensure that you don't have any uncommitted changes by running git status (and if you have any uncommitted changes, run git commit -am 'your-message' to commit them) then run:

$ movable deploy production

Note: Currently, the first time a new app is pushed, it must be enabled by MI Production Support. Subsequent pushes are automatically enabled. This will be streamlined in the future.

This will push your current branch to the production platform app. Any time a user selects your app from the App Gallery, they will be using your updated code. Existing apps that users have created will not be affected.