Updating

AirTrail shows a notice in the app when a new version is available, to the owner and administrators by default. Read the release notes before updating, especially for a new major version.

Docker ComposeCopy Anchor Link

In the directory with docker-compose.yml and .env, run:

docker compose pull
docker compose up -d

The container applies database migrations automatically when it starts. Check docker compose logs airtrail if the app does not come back up.

Pinning a versionCopy Anchor Link

The Compose file uses the latest tag, which moves to each new release when you pull. To update only when you choose, pin a specific version in docker-compose.yml:

  airtrail:
    image: johly/airtrail:v3.12.0

To update, change the tag to the new version and run the commands above. A major-version tag such as v3 follows new releases within that major version but never jumps to the next one, which avoids surprise breaking changes. Available tags are listed on Docker Hub.

Rolling backCopy Anchor Link

1. Stop AirTrail with docker compose down.
2. Set the image tag back to the version you were running before.
3. Restore the database backup taken before the update, as described in Backup and restore.
4. Start AirTrail with docker compose up -d.

PortainerCopy Anchor Link

Open the stack, then Editor → Update the stack with Re-pull image and redeploy enabled.

Manual installationCopy Anchor Link

Stop AirTrail, then in the installation directory:

git fetch --tags
git checkout "$(git describe --tags "$(git rev-list --tags --max-count=1)")"
bun install
bun run build
bun run db:migrate-deploy

Start AirTrail again, for example with sudo systemctl start airtrail.

If you use the optional airport map layer, copy the latest airport-overlay.pmtiles into static/ again before bun run build. See Manual installation.