Some checks failed
cc-ci/testme cc-ci: failure
backup-bot-two 2.4.0 snapshots paths INSIDE named volumes (backupbot.backup.volumes.<vol>.path, relative to the volume root) and IGNORES the old backupbot.backup.path label. The db pre-hook wrote /postgres.dump.gz to the container's ephemeral root fs — outside every volume — so the dump never reached the snapshot and the restore post-hook failed on a missing file (gzip: /postgres.dump.gz: No such file). - db: dump into the db-data volume (transient; hooks remove it) and snapshot only that file via backupbot.backup.volumes.db-data.path — same pattern as keycloak, which passes backup/restore on this CI. Also use $POSTGRES_DB in the restore hook: the previous $PLAUSIBLE_DB is defined nowhere and only connected via libpq's username fallback. - clickhouse: snapshot only backup/events (the clickhouse-backup output) inside the event-data volume instead of the whole volume — restoring raw data files under a running server is unsafe; the post-hook performs the logical restore.
113 lines
4.4 KiB
YAML
113 lines
4.4 KiB
YAML
---
|
|
version: "3.8"
|
|
|
|
services:
|
|
app:
|
|
image: plausible/analytics:v2.0.0
|
|
command: sh -c "sleep 10 && /entrypoint.sh db createdb && /entrypoint.sh db migrate && /entrypoint.sh run"
|
|
depends_on:
|
|
- db
|
|
- plausible_events_db
|
|
environment:
|
|
- BASE_URL=https://$DOMAIN
|
|
- SECRET_KEY_BASE
|
|
- DATABASE_URL=postgres://plausible:plausible@${STACK_NAME}_db:5432/plausible
|
|
- CLICKHOUSE_DATABASE_URL=http://${STACK_NAME}_plausible_events_db:8123/plausible_events_db
|
|
- SMTP_HOST_ADDR
|
|
- MAILER_EMAIL
|
|
- SMTP_HOST_PORT
|
|
- SMTP_USER_NAME
|
|
- SMTP_USER_PWD
|
|
- SMTP_HOST_SSL_ENABLED
|
|
- DISABLE_REGISTRATION
|
|
- DISABLE_AUTH
|
|
networks:
|
|
- proxy
|
|
- internal
|
|
deploy:
|
|
restart_policy:
|
|
condition: on-failure
|
|
labels:
|
|
- "traefik.enable=true"
|
|
- "traefik.http.services.${STACK_NAME}.loadbalancer.server.port=8000"
|
|
- "traefik.http.routers.${STACK_NAME}.rule=Host(`${DOMAIN}`${EXTRA_DOMAINS})"
|
|
- "traefik.http.routers.${STACK_NAME}.entrypoints=web-secure"
|
|
- "traefik.http.routers.${STACK_NAME}.tls.certresolver=${LETS_ENCRYPT_ENV}"
|
|
- coop-cloud.${STACK_NAME}.version=3.1.0+v2.0.0
|
|
db:
|
|
image: pgautoupgrade/pgautoupgrade:18-alpine
|
|
volumes:
|
|
- db-data:/var/lib/postgresql/data
|
|
environment:
|
|
# pin legacy PGDATA so the existing cluster on the volume is upgraded in place, not re-init'd
|
|
- PGDATA=/var/lib/postgresql/data
|
|
- POSTGRES_USER=plausible
|
|
- POSTGRES_PASSWORD=plausible
|
|
- POSTGRES_DB=plausible
|
|
networks:
|
|
- internal
|
|
healthcheck:
|
|
test: ["CMD-SHELL", "pg_isready -U plausible -d plausible"]
|
|
interval: 5s
|
|
timeout: 5s
|
|
retries: 60
|
|
deploy:
|
|
labels:
|
|
backupbot.backup: "true"
|
|
# backup-bot-two v2 snapshots paths INSIDE named volumes (backupbot.backup.volumes.<vol>.path,
|
|
# relative to the volume root) and ignores the old `backupbot.backup.path` label — a dump
|
|
# written to the container root fs never reaches the snapshot, so restore finds nothing.
|
|
# The dump therefore lives (transiently — the hooks remove it) at the db-data volume root.
|
|
backupbot.backup.volumes.db-data.path: "postgres.dump.gz"
|
|
backupbot.backup.pre-hook: sh -c 'pg_dump -U "$$POSTGRES_USER" -Fc "$$POSTGRES_DB" | gzip > /var/lib/postgresql/data/postgres.dump.gz'
|
|
backupbot.backup.post-hook: "rm -f /var/lib/postgresql/data/postgres.dump.gz"
|
|
backupbot.restore: "true"
|
|
backupbot.restore.post-hook: sh -c 'gzip -d /var/lib/postgresql/data/postgres.dump.gz && pg_restore --clean -U "$$POSTGRES_USER" --dbname="$$POSTGRES_DB" < /var/lib/postgresql/data/postgres.dump && rm -f /var/lib/postgresql/data/postgres.dump'
|
|
|
|
plausible_events_db:
|
|
image: clickhouse/clickhouse-server:23.4.2.11-alpine
|
|
volumes:
|
|
- event-data:/var/lib/clickhouse
|
|
entrypoint: /custom-entrypoint.sh
|
|
configs:
|
|
- source: clickhouse-config
|
|
target: /etc/clickhouse-server/config.d/logging.xml
|
|
- source: clickhouse-user-config
|
|
target: /etc/clickhouse-server/users.d/clickhouse-user-config.xml
|
|
- source: clickhouse_entrypoint
|
|
target: /custom-entrypoint.sh
|
|
mode: 0555
|
|
networks:
|
|
- internal
|
|
deploy:
|
|
labels:
|
|
backupbot.backup: "true"
|
|
# v2 volumes-include syntax (see db service): snapshot only the clickhouse-backup output
|
|
# inside the event-data volume — not the live raw data files (restoring those under a
|
|
# running server is unsafe; the restore post-hook performs the logical restore instead).
|
|
backupbot.backup.volumes.event-data.path: "backup/events"
|
|
backupbot.backup.pre-hook: clickhouse-backup create events
|
|
backupbot.backup.post-hook: "rm -rf /var/lib/clickhouse/backup/events"
|
|
backupbot.restore: "true"
|
|
backupbot.restore.post-hook: clickhouse-backup restore --rm events && rm -rf /var/lib/clickhouse/backup/events
|
|
|
|
volumes:
|
|
db-data:
|
|
event-data:
|
|
|
|
networks:
|
|
proxy:
|
|
external: true
|
|
internal:
|
|
|
|
configs:
|
|
clickhouse-config:
|
|
name: ${STACK_NAME}_clickhouse_config_${CLICKHOUSE_CONF_VERSION}
|
|
file: clickhouse-config.xml
|
|
clickhouse-user-config:
|
|
name: ${STACK_NAME}_clickhouse_user_config_${CLICKHOUSE_USER_CONF_VERSION}
|
|
file: clickhouse-user-config.xml
|
|
clickhouse_entrypoint:
|
|
name: ${STACK_NAME}_clickhouse_entrypoint_${CLICKHOUSE_ENTRYPOINT_VERSION}
|
|
file: entrypoint.clickhouse.sh
|