Deployments & backups

Every publish creates a deployment, and every deployment is retained. That gives you a full history you can review and roll back to, plus separate point-in-time recovery for a site's data.

Deployment history

The app lists a site's deployments with what changed and when. From there you can roll back to any previous deployment, which re-publishes that version and takes it live. The same is available from the CLI:

acira deployments        # list history
acira rollback <id>      # re-publish a previous version

Rolling back is a normal publish of an older version, so it's safe and reversible — you can roll forward again.

Backups and point-in-time recovery

Code rollback restores the site; backups restore the data. A site's recent data can be recovered to an earlier point in time, independently of deployments — useful if a bad import or a mistaken bulk change corrupted records. From the CLI:

acira backup bookmark     # mark a known-good point
acira backup restore      # restore data to a point in time
acira backup undo         # reverse a restore
acira backup list

Logs

Alongside history, the app surfaces a site's errors and recent console output, and acira logs shows the same from the terminal — so when something misbehaves after a publish, you can see what happened and roll back if needed.