Deployments take source-code created by you and your team, install the necessary dependencies, and deploy it to the services in your stack. This way, the same source-code based on a programming language is in sync across all your Web Services, Workers, and Jobs in the same stack.
All you have to do is to navigate to a directory in your file system with the source-code you intent to deploy and run the following command:
The system automatically picks the most convenient formula application based on a simple heuristic: If a Dockerfile is present in the directory, the first time you deploy to the stack, the source code is built and deployed using the Dockerfile formula. Otherwise, the platform switches the stack to use Buildpacks for the current and all subsequent deployments.
mesh deploy command captures the live output of the build process, the release command(if you have any), and a few lines of code of any Worker or Web Service enabled in the stack until the deployment is considered successful.
To get a list of current and past deployments, you can use the following command:
mesh deployments list
Deployments version incrementally, starting with
v0 for easy reference.
To see the live output of deployment or see the output log of an old build, you can use
mesh deployments show as in:
mesh deployments show v2
The platform records the deployment’s output for later inspection, so you don’t need a separate command to inspect past deployments.
Once the deployment process successfully, the services are updated. To inspect the status of every service, you can run:
mesh services list