Updating

What changed in each version — What's new.

From the admin panel with rollback coming soon

A “Settings → Updates” page is being prepared: current and available version, changelog, “Update” and “Roll back” buttons, update history. An update will take and verify a backup, show a short maintenance page, apply migrations, check health and roll back to the previous version on failure. Docker on the server will be handled by a separate host service, not by the website.

Manually

For now an update is installed the same way as the installation: a new release archive and the same script.

1. Backup. Settings → Backups → “Back up now”. Wait until the copy appears in the list.

2. Unpack the new release over the installation folder. The .env file and data (database, backups, client documents) are stored separately and are not overwritten.

3. Run the script with your domain:

   bash infra/server/04-deploy.sh example.com

   It builds images, validates the Caddy config, applies database migrations and restarts services. If the Caddy config has an error, the script stops and the site keeps working.

4. Check:

   curl -s https://example.com/api/health

   The response shows the new version and "status":"ok".

Removed files

Unpacking over the folder does not delete files that are no longer in the release. If the release notes say to delete a file, delete it manually.

If something goes wrong

• The site does not open — Troubleshooting.
• You need the data from before the update — Restore from backup.