Releases

After a successful deployment, your deployment is consider a release and is stored in a Release table. You can have up to 4 releases at once.

Rollbacks

Amezmo defines a release "Rollback" as changing the active release to a previous release. Rolling back your current release to a previous release does not trigger a new deployment. A rollback is an atomic operation. Your web application will begin serving files from your previous release immediately. Your workers are also reloaded after your symbolc link is updated. See below for the list of hooks Amezmo will look for when you execute a rollback operation.

Hooks

Upon rolling back your current release, Amezmo will execute the following scripts:

.amezmo/rollback/before

This script is executed before updates your current directory

.amezmo/rollback/after

This script is executed after the symbolic link directory is updated.

Note: The scripts that are executed are the scripts defined in your current release. This means that when you execute a rollback, the scripts that will run are the ones that exist in your current release directory, not the target rollback.

Limits

At this time, you can have 4 releases. Amezmo keeps your last 4 most recent releases.

Need support?

We're always happy to help with either application or infrastructure questions Always feel free to reach out to us on Twitter, or contact support.

Subscribe