deploy/pobsync.env.example

POBSYNC_DJANGO_DEBUG=0
POBSYNC_DJANGO_SECRET_KEY=change-me-to-a-long-random-secret
POBSYNC_DJANGO_ALLOWED_HOSTS=backup.example.com,localhost,127.0.0.1
POBSYNC_DJANGO_CSRF_TRUSTED_ORIGINS=https://backup.example.com

POBSYNC_HOME=/var/lib/pobsync
POBSYNC_BACKUP_ROOT=/backups
POBSYNC_SQLITE_PATH=/var/lib/pobsync/pobsync.sqlite3
POBSYNC_STATIC_ROOT=/var/lib/pobsync/static
POBSYNC_ENV_FILE=/etc/pobsync/pobsync.env
POBSYNC_SERVICE_USER=pobsync
POBSYNC_SERVICE_GROUP=pobsync

POBSYNC_WEB_BIND=127.0.0.1:8010
POBSYNC_GUNICORN_WORKERS=2
POBSYNC_GUNICORN_TIMEOUT=120
POBSYNC_WORKER_INTERVAL=15
POBSYNC_SCHEDULER_INTERVAL=60
(refactor) Add native systemd production deployment Make native systemd services the recommended production path for pobsync while keeping Docker Compose available for development and optional test installs. Add web, worker, and scheduler systemd unit templates, a native environment example, an optional nginx reverse proxy template, and an installer that creates the venv, service user, env file, units, and runs migrations/static collection. Allow native deployments to configure POBSYNC_BACKUP_ROOT directly and document the new production layout and update flow. 2026-05-19 15:59:07 +02:00			`POBSYNC_DJANGO_DEBUG=0`
			`POBSYNC_DJANGO_SECRET_KEY=change-me-to-a-long-random-secret`
			`POBSYNC_DJANGO_ALLOWED_HOSTS=backup.example.com,localhost,127.0.0.1`
			`POBSYNC_DJANGO_CSRF_TRUSTED_ORIGINS=https://backup.example.com`

			`POBSYNC_HOME=/var/lib/pobsync`
			`POBSYNC_BACKUP_ROOT=/backups`
			`POBSYNC_SQLITE_PATH=/var/lib/pobsync/pobsync.sqlite3`
			`POBSYNC_STATIC_ROOT=/var/lib/pobsync/static`
(ops) Expand native install self checks and recovery docs Extend the runtime self check with native install diagnostics for the environment file, service user, backup root ownership, and SQLite database path. Export install metadata from the systemd units and pobsync-manage wrapper so custom env files and service users are visible to Django checks. Document restart, journal log inspection, and rollback steps in the README so production updates have a clear recovery path. 2026-05-20 01:44:51 +02:00			`POBSYNC_ENV_FILE=/etc/pobsync/pobsync.env`
			`POBSYNC_SERVICE_USER=pobsync`
			`POBSYNC_SERVICE_GROUP=pobsync`
(refactor) Add native systemd production deployment Make native systemd services the recommended production path for pobsync while keeping Docker Compose available for development and optional test installs. Add web, worker, and scheduler systemd unit templates, a native environment example, an optional nginx reverse proxy template, and an installer that creates the venv, service user, env file, units, and runs migrations/static collection. Allow native deployments to configure POBSYNC_BACKUP_ROOT directly and document the new production layout and update flow. 2026-05-19 15:59:07 +02:00
			`POBSYNC_WEB_BIND=127.0.0.1:8010`
			`POBSYNC_GUNICORN_WORKERS=2`
			`POBSYNC_GUNICORN_TIMEOUT=120`
			`POBSYNC_WORKER_INTERVAL=15`
			`POBSYNC_SCHEDULER_INTERVAL=60`