Updating

Kurir is distributed as a Docker image via GitHub Container Registry (ghcr.io/cfarvidson/kurir-server:latest). Updating pulls the latest image and restarts the app. Database migrations run automatically on startup, so no manual migration step is needed.

Before updating

It is a good idea to create a backup before updating, especially for major versions:

docker compose -f docker-compose.production.yml exec app sh scripts/kurir-backup.sh

One-command installer users

If you used the one-command installer, your installation lives at /opt/kurir/.

cd /opt/kurir
docker compose pull
docker compose up -d

This pulls the latest images for all services (app, PostgreSQL, Redis, Caddy) and restarts any containers that have changed. Database migrations are applied automatically when the app starts.

Docker Compose (manual) users

cd /path/to/kurir-server
docker compose -f docker-compose.production.yml pull
docker compose -f docker-compose.production.yml up -d

Kamal users

kamal deploy

Kamal builds and pushes a new image from the current codebase, then performs a rolling deploy. The post-deploy hook automatically runs prisma db push to apply any schema changes.

Database migrations

Database migrations run automatically on application startup. You do not need to run them manually.

If you are using Kamal, the post-deploy hook handles prisma db push. The search vector migration (for full-text search) must be run manually once on first install:

kamal app exec "npx prisma db execute --file prisma/migrations/search_vector.sql"

Checking for updates

Kurir does not have a built-in update notification system. To check for new releases:

• Watch the GitHub repository for new releases.
• Compare your running image digest with the latest:

# See what you're running
docker inspect ghcr.io/cfarvidson/kurir-server:latest --format '{{.Id}}' 2>/dev/null

# Pull latest and compare
docker pull ghcr.io/cfarvidson/kurir-server:latest

Rolling back

If an update causes issues, you can roll back to a previous image. First, find the previous image digest in your Docker history, then pin to it:

# List recently pulled images
docker image ls ghcr.io/cfarvidson/kurir-server

# Restart with a specific digest
# Edit docker-compose.yml to pin: image: ghcr.io/cfarvidson/kurir-server@sha256:abc123...
docker compose up -d

Alternatively, restore from a backup taken before the update (see Backup & Restore).