Torrin ships as versioned container images. To update:
Use the same overlay flags you started with, e.g.:
docker compose up -d alone does not re-pull images — always run pull
first, or a service can keep running an old image.
Notes
- Database changes apply automatically on startup (the schema is embedded),
so there’s no manual migration step.
- Config is your
.env; new options land in .env.example — diff it against
your .env after pulling to pick up anything new.
- To pin a specific version instead of the latest, set
TORRIN_TAG in .env.