Rollback

A rollback is a rebuild of the application images from an older git ref and a restart of the application containers. Postgres, Redis, the edge, the certificates and the schema are untouched. Because the installer builds images on the box under one tag, there is no older image to point at; the git ref is the thing you know.

Roll back

cd /srv/themerchantengine
bash deploy/scripts/rollback.sh v1.0.0

The script resolves the ref before it moves anything, checks it out, rebuilds the API, admin and storefront images the running stack declares, and restarts only those containers. Postgres and Redis keep running; customers see the storefront answer again within the image build time.

When the release you are leaving changed the schema

The older code may not read the newer tables. Restore the dump taken before the update first, as Backups and restore describes, then roll the code back, and take the outage that implies. There is no automated schema rollback, which is why every update starts with a dump.

After a rollback

The checkout is now at the older ref. A later ./setup.sh on that checkout re-renders the stack from that release’s templates and is a full re-run of the installer for it, which is fine and idempotent. When the fix for whatever made you roll back ships, update the normal way: Update the store.