Docs

Self-hosted

Upgrades

Back up, rebuild with Docker Compose, and check the version. An older release refuses to start on a database a newer one has upgraded.

Upgrades are one-way. To go back, restore the backup you took before upgrading. An older release refuses to start on a database that a newer one has already upgraded, rather than writing an incompatible schema.

Rebuild

  1. Take a backup of the database and the file volume.
  2. Get the new release into the same folder and rebuild.
docker compose up -d --build
  1. Check what is running. GET /api/meta reports the version and the database schema.

Migrations run when the API starts. You do not apply them by hand.

Installs that predate sign-in

A release from before 28 October 2026 had no passwords. After this upgrade the app asks people to sign in, and nobody has a password yet. In the API container, run:

docker compose exec api node dist/auth/bootstrap-cli.js

Add --email [email protected] to name the administrator. The command prints a one-time link, valid for 24 hours. Open it, choose a password, then invite the others from Team. Their history stays.

To keep the old open behaviour instead, set ANIMSYNC_ACCESS=open in .env and rebuild. That is a trusted LAN only: anyone who can reach the port can read and publish.