Maintenance

Day-to-day operation once the stack is running.

Updating

Images are tagged latest. To move to the newest release, pull and recreate:

docker compose pull
docker compose up -d

Your data lives in volumes, so updates keep accounts, history, and downloads. Only the containers are replaced. Check everything came back up:

docker compose ps

Logs

docker compose logs -f typetype-server     # follow one service
docker compose logs --tail=100 typetype    # last 100 lines of the web app
docker compose logs                         # everything

The server logs are the place to look when extraction, accounts, or the API misbehave.

Backups

Two stores hold everything that matters: the database and the object store.

Database

docker compose exec -T postgres \
  pg_dump -U typetype typetype > typetype-$(date +%F).sql

Restore into a fresh stack:

cat typetype-YYYY-MM-DD.sql | docker compose exec -T postgres psql -U typetype typetype

Object store (downloads)

The downloads are in the garage_data and garage_meta volumes. Back up the volumes themselves (stop the stack first for a consistent copy):

docker compose down
docker run --rm -v typetype_garage_data:/data -v "$PWD":/backup busybox \
  tar czf /backup/garage-data-$(date +%F).tar.gz -C /data .
docker compose up -d

Adjust the volume name if your Compose project prefix differs (see it with docker volume ls).

TIP

Downloads are regenerable artifacts, so the database backup is the important one. The .env file is also worth keeping, since it pins your ports and any custom values.

Stopping and starting

docker compose stop      # stop containers, keep them
docker compose start     # start them again
docker compose down      # remove containers, keep volumes (data safe)

Resources

A small instance is comfortable on ~2 GB of RAM. The heaviest components are the API server (JVM) and the database. The downloader does the most disk and network work while jobs run; it is idle otherwise.