# Deploy a repeatable release

Source: https://zotonic.com/docs/2994/deploy-a-repeatable-release

URI: https://zotonic.com/id/2994

Language: en

Record the code revision, build steps, configuration changes, and schema changes for the release. Build and test the same revision in an acceptance environment first.

Before deployment, verify that the required database and file backups can be recovered. Apply code and configuration in the planned order and monitor startup and upgrade logs. Confirm the intended sites and modules are running.

::: {.aside}
See also [deploy: Pull, compile and activate code](/docs/3133/deploy-pull-compile-and-activate-code "deploy: Pull, compile and activate code")
:::

Finish with an HTTP check and one representative user workflow. A responding Erlang node is only one part of readiness. Keep a recovery plan that accounts for both code and database changes.

License: 

Attribution: 

Related resources: https://zotonic.com/api/agent/related/2994?language=en


## API access

- [API help](<https://zotonic.com/api-help>)
- [OpenAPI specification](<https://zotonic.com/openapi.json>)
- [This resource as JSON](<https://zotonic.com/api/agent/resource/2994?language=en>)
