Deploy

This command starts the deploy and follows the build and release:

blossom environment:deploy --id environment-100 --follow

Blossom builds the image, starts the new Containers, waits for configured health checks, and then sends them traffic.

For your own App, the first deployment is also a chance to check the build and startup configuration. If it fails, inspect the Activity and logs, adjust the settings, and deploy again:

blossom environment:activity --id environment-100
blossom activity:logs --id activity-100
blossom logs --environment environment-100

Need a console inside the Container? Use Blossom Shell, including the launcher example for buildpack images.

Deploy On Push

Enable Automated Deploys in the Environment’s Source and Build settings. A push to its configured branch builds that push’s exact commit.

If you push again during a deployment, the running deployment continues. Only the newest waiting deployment runs next; older waiting attempts are marked skipped. Each attempt keeps its own commit.

What You Get

Your App, live at the Environment’s URL, printed as Open: when the deploy finishes:

Everything that happened is a command away:

blossom release:list --environment environment-100
blossom activity:list
blossom logs --environment environment-100

Deploy again whenever you change the code or settings. To undo a deploy, blossom release:rollback returns to an earlier Release.

Next, clean up when you’re done trying it out.