Spaces:
Paused
Paused
Commit History
-
fix backup status display, sync loop spin, and PM2 log leakage
- postiz-sync.py: cmd_sync/cmd_restore now write status+message fields alongside db_status so dashboard can show BACKUP: SUCCESS/ERROR/RESTORED (previously only db_status was written; dashboard reads status/message) - start.sh: sanitize SYNC_INTERVAL (strip non-digits, clamp ≥60s) to prevent sleep "" failure causing tight infinite sync loop at startup - start.sh: extend PM2 grep filter to drop backslash ASCII art (\\{4,}), PM2 log headers (/root/.pm2/...log last N lines), and > pm2 command echoes Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>4a7c78e
-
feat(sync): skip backup when no state changes detected
Add pg_stat_database activity marker + filesystem markers for uploads, secrets, and .next BUILD_ID. State persisted to /tmp; backup skipped when markers match the last successful upload's snapshot. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>a9c0f66
-
reduce startup log verbosity
start.sh: - Expand grep -Ev filter (fix multi-arg syntax → -e flags): suppress [InstanceLoader], [PM2] infra msgs, Prisma package install, pnpm script echo headers, /root/.pm2/logs/ paths, PM2 ASCII art, blank lines, apps/X pm2: lines - "Postgres ready/Starting Redis/Redis ready" → "✓ Postgres/✓ Redis" - "Starting nginx + Postiz PM2 procs" → "Starting Postiz..." - "Waiting for nginx" → "Waiting for Postiz..." postiz-sync.py: - Logger format: "YYYY-MM-DD HH:MM:SS - INFO - msg" → "[sync] msg" - Demote "Database dumped" + "Tarball created" to DEBUG (not shown) Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>2272bb9
-
fix: adjust OAuth callback paths, force /app root redirect, and increase logging verbosity for sync processes
3d8fd70 -
refactor: implement two-pass backup creation to automatically exclude frontend cache if tarball exceeds size limits
264b68d
-
fix: move next build to container startup — HF builder cgroup too small
next build for Postiz needs ~4 GB RSS. The HF Space builder has a ~4 GB cgroup limit, making it impossible to complete in docker build regardless of heap tuning, single-thread flags, or multi-stage tricks (exit 137). Solution: don't run next build in the Dockerfile at all. Run it in start.sh at container startup where the runtime has 16 GB RAM. Bonuses over the docker-build approach: - NEXT_PUBLIC_BACKEND_URL is baked with the real SPACE_HOST URL (correct) instead of localhost (broken) because we now know it at build time - First boot ~5-8 min; all subsequent boots restore .next from HF Dataset backup and skip the build entirely Changes: - Dockerfile: remove all frontend build steps; back to clean 2-stage; HEALTHCHECK start-period raised to 600s for first-boot window - start.sh: build frontend at startup if .next/BUILD_ID absent; 8 GB heap (runtime has 16 GB); shows progress in logs - postiz-sync.py: include .next (minus webpack cache) in backup tarball; restore on boot so…866a8e6 -
initialize project
b4d7c1c