Upgrades
An upgrade is a new binary or image over the same SQLite file. Schema changes run at startup: missing tables are created and missing columns added, so there are no migrations to run by hand.
Back up the database.
Get the new version and restart:
Install Update Docker docker pull ghcr.io/karanjot786/trail, thendocker rm -f trailand the samedocker runas beforeCompose docker compose pull && docker compose up -dInstall script Run the install command again. It replaces the binary and restarts trail.service, leaving/etc/trail.envand the data aloneFrom source git pull && make build, thensystemctl restart trail(ordocker buildand recreate the container)Fly.io git pull && fly deployPin a version to choose when you move:
ghcr.io/karanjot786/trail:0.3(or:0.3.1), orTRAIL_VERSION=v0.3.1for the install script.:edgefollows themainbranch.
The tracker files are embedded in the binary, so sites that load /_t/t.js get the new tracker as soon as the server restarts. They are served with Cache-Control: public, max-age=3600, so browsers pick them up within an hour.
Read the changelog before upgrading.
Next
- Check the changelog for what changed.
- If events stop after the upgrade, see Troubleshooting.