GitBlixt
Docs Navigation

Upgrading

GitBlixt upgrades are designed to be safe and fast. Database migrations run automatically on startup.

Standard Upgrade

docker pull gitblixt/gitblixt:latest
docker stop gitblixt
docker rm gitblixt
docker run -d \
  --name gitblixt \
  --restart unless-stopped \
  -p 80:80 -p 443:443 -p 22:22 \
  -e GITBLIXT_HOST=git.yourdomain.com \
  -e GITBLIXT_SECRET_KEY_BASE=your-secret \
  -v gitblixt_data:/data \
  gitblixt/gitblixt:latest

Your data volume (gitblixt_data) is preserved. The new container runs migrations automatically before accepting traffic.

Upgrading to a Specific Version

Replace latest with a version tag to pin to a specific release:

docker pull gitblixt/gitblixt:1.2.0

Before Upgrading

  1. Read the release notes for the version you're upgrading to — especially any breaking changes or manual migration steps.
  2. Take a backup before every upgrade. See Backup & Restore.

Rollback

If something goes wrong after an upgrade:

  1. Stop the current container
  2. Start the previous image version (you'll need the old image tag)
  3. Restore your database from the pre-upgrade backup