Updating

Bittery publishes new Docker images to ghcr.io/bittery-org with every release. Database migrations run automatically on server startup — no manual migration step is needed.

Docker Compose

Pull the latest images

cd ~/bittery
docker compose pull

Restart the services

COMPOSE_PROFILES=builtin-db docker compose up -d

Adjust COMPOSE_PROFILES to match your setup (e.g. builtin-db,storage,cache).

Verify

docker compose ps

All services should show (healthy) within a minute.

Tip

You can combine both steps into a single command:

docker compose pull && COMPOSE_PROFILES=builtin-db docker compose up -d

Railway

  1. Go to your Railway project dashboard
  2. Click Redeploy on the server and web services
  3. Railway pulls the latest images automatically

Rollback

If something goes wrong after an update, you can roll back to a specific version:

# Pin a specific version in docker-compose.yml or use:
docker compose down
docker compose pull ghcr.io/bittery-org/bittery-server:v1.2.3
docker compose pull ghcr.io/bittery-org/bittery-web:v1.2.3
docker compose up -d

Warning

Database migrations are forward-only. If you roll back to an older server version, ensure the database schema is still compatible. For major version upgrades, always back up your database first.

Monitoring

Check the health of your instance at any time:

# Service status
docker compose ps

# Server logs
docker compose logs -f server

# Health endpoint
curl https://your-domain.com/healthz
PreviousConfiguration Reference