Files
inbuxa-installer/e2e
jcoffey-dev 27c2fc9de8 Keep the server's data on its named volumes, and move older installs there
compose.yaml mounted inbuxa-etc and inbuxa-data at /opt/stalwart/etc and
/opt/stalwart/data, where the server never looks. The image keeps its
configuration and mail in /etc/inbuxa and /var/lib/inbuxa, so they went
into anonymous volumes: a `docker compose down` and `up` started the server
empty, in bootstrap mode, and backups of the named volumes held nothing.

The named volumes are now mounted where the server keeps its data. An
install made before this is moved over on its next run, before anything is
recreated, since recreating it first would lay the empty named volumes over
the real data: the server is stopped, each anonymous volume is copied into
its named one, and the run checks the server comes back configured rather
than in bootstrap mode. A named volume that already holds something is
never overwritten; the server is started again as it was and the run
stops. The old anonymous volumes are kept, so the move can be undone.

e2e/cases/upgrade-volumes.sh installs with an installer from before this
(OLD_REF, built by run.sh), upgrades, and checks the first mailbox still
signs in after the upgrade, after a down and up, and on a further run.

Fixes #5
2026-10-04 23:12:12 -07:00
..