Let’s deploy a new release
To do this, run
b4a deploy from the command line:
This pushes the new code (in
public) to the Parse Cloud and deploys this code for the default target which is the first app that was added or the one you set using
b4a default.You can choose to deploy to a different target by adding the target as an argument to
You can add release notes to the deploy with the
If the contents of your Back4App project remain unchanged then we skip deploy. You will see an output like:
$ b4a deploy app_name Uploading source files Finished uploading files
Not creating a release because no files have changed
You can override this behavior with the
--force flag. Providing this flag forces a deploy despite no changes to your project.
When embedding parse deploy within other scripts (such as in an automated testing/deploy environment) you can rely on the exit code from the Parse command line tool to indicate whether the command succeded. It will have an exit code of 0 on success and a non-zero exit code when the deploy failed.