VAULTHandbook
deen

Installing updates

Unpack the new version, one command — with a backup first and rollback on failure.

An update is two steps: unpack the new version over the existing folder (your .env, storage and backups stay put), then run update.sh.

On the server, in the VAULT folder
unzip -o vault-new.zip -d /opt/vault
cd /opt/vault
bash update.sh

What update.sh does, in this order

  1. 1

    Backup first

    Before anything is touched, the script takes a full backup (database, files, .env). If that fails, it asks — and refuses to continue without your explicit yes.

  2. 2

    Remember the running image

    The currently running version is tagged vault:previous — that is the way back.

  3. 3

    Build and start the new one

    The build runs while your store keeps serving — only the restart switches versions. Migrations run automatically on boot.

  4. 4

    Health check — or roll back

    If the new version does not report healthy within three minutes, the script restores the previous version by itself and tells you where to look.

Which version is running is always visible at https://your-domain.com/api/health — and what changed, in the bundled CHANGELOG.md.