First deploy

A step of the Cloud application tree on Gradus, in the Environment setup area: First commit to first deploy.

Prove the deploy from CI: a post-deploy job that calls the public health route, checks it reports the commit just merged and fails the workflow when it does not. This walking skeleton is what every other step grows from.

Usually comes after: Choose where to run, any option of Cloud provider.

Leads to: One-command rollback, Secrets management, Structured logging, Choose a database.

Prompt for your AI assistant

Make the /health route report the commit it was built from, passed in at build time. Add a post-deploy job to the CI workflow that waits for the new revision to be live, calls the public /health URL and fails the workflow when it does not return 200 with the commit just merged within two minutes, so a deploy that quietly left the old version running fails too. Print the public URL in the workflow summary and put it at the top of the README.

• Show on map
• This step as Markdown
• Every step of the tree, for AI assistants

This is https://gradus.kazet.blog/tree/cloud-application/step/first-deploy as plain HTML. In a browser the page also lets you mark the step forged and copy a message for your AI assistant.