Upgrade
Move to a new DBTrail version in three commands. Your servers, your password, the copy and its history carry over.
Three commands, from the dbtrail folder the Quick Start created. Your .env,
your servers, your web interface password, the copy and its history all carry
over.
# 1. The new version
docker compose pull
# 2. The current compose file, saved NEXT to yours, so your own edits are kept
curl -fsSL -o docker-compose.yml.new https://raw.githubusercontent.com/dbtrail/dbtrail/main/docker-compose.yml
diff docker-compose.yml docker-compose.yml.new # carry any edits you made into the new file
mv docker-compose.yml.new docker-compose.yml
# 3. Restart on the new version
docker compose up -dDo not skip step 2. The compose file is what wires the volumes, the ports
and the MySQL port on 3309, and nothing else updates it. With an old file, a
new version can start without the MySQL port, or forget the password and the
servers you added the next time a container is recreated. When something your
file lacks is not in effect, docker compose logs bintrail says so at startup,
with the fix.
The web interface opens with your servers, and Status shows capture running. A MySQL client connects to port 3309 as before.
Installed another way
- Linux packages (.deb or .rpm): Upgrade.
- Amazon ECS: point the task definition at the new image tag and update the service: Deployments.
- DBTrail EE: Upgrading DBTrail EE.
What changed between versions, and what each file version adds: release notes and Upgrading the stack.