docker app hosting with backups

If you want to host an app with Docker and have backups, the usual setup is:

1) Run the app in a container

Use Docker Compose so the app, database, and any supporting services are defined together.

Example:

services:
  app:
    image: your-app:latest
    ports:
      - "80:3000"
    restart: unless-stopped
    volumes:
      - app_data:/app/data

  db:
    image: postgres:16
    environment:
      POSTGRES_USER: app
      POSTGRES_PASSWORD: secret
      POSTGRES_DB: appdb
    volumes:
      - db_data:/var/lib/postgresql/data
    restart: unless-stopped

volumes:
  app_data:
  db_data:

2) Back up persistent data

Docker containers themselves are disposable, so back up:

• Named volumes or bind mounts
• Database dumps from PostgreSQL/MySQL/MariaDB
• Config files like docker-compose.yml, .env, reverse proxy config

3) Backup strategies

For databases

Use logical backups:

• PostgreSQL: pg_dump
• MySQL/MariaDB: mysqldump

Example PostgreSQL backup:

docker exec -t your-postgres-container pg_dump -U app appdb > backup.sql

For volumes

If data is stored in a Docker volume:

docker run --rm \
  -v db_data:/volume \
  -v $(pwd):/backup \
  alpine tar czf /backup/db_data-backup.tar.gz -C /volume .

4) Automate backups

Use cron on the host, or a backup container/script that:

• Creates a database dump
• Archives important volumes
• Uploads to offsite storage like S3, Backblaze B2, or another server
• Keeps multiple restore points

5) Don’t forget restore testing

A backup is only useful if you can restore it. Periodically test:

• restoring the DB dump
• recreating containers from Compose
• restoring volumes

6) Recommended production setup

• Docker Compose
• Reverse proxy: Caddy / Nginx / Traefik
• Persistent volumes for data
• Automated backups to offsite storage
• Monitoring + restart policy

If you want, I can give you:

1. a simple Docker Compose hosting setup,
2. a backup script, or
3. a full production example with Postgres + automatic backups.