Publish Docs Site / build (push) Failing after 5s
- mkdocs.yml with dark slate theme, nav for 12 ITPP projects - build-docs.sh aggregates docs from all project repos - .gitea/workflows/docs-publish.yml for nightly rebuild+deploy - README and CHANGELOG for the itpp-docs repo itself - docs-source/ populated from all 12 repos - site/ ready for deployment to docs.itpropartner.com
1.5 KiB
1.5 KiB
Backup-Restore Changelog
2026-07-20 — Restore logging and manual backup
Added
- Backup Now button: Green "+ Backup Now" button on backup page
- Domain dropdown: Select element with all 9 hosted domains
- Note field: Optional "why" note saved as note.txt in snapshot
- Restore History section: Auto-expanded table at bottom — Domain, Snapshot, Date/Time, Status
- Restore logging: Every restore writes to
/opt/backup-restore/logs/restore.log - Status formatting: Green OK / red FAILED with centered status column
Fixed
- Restore timing out: Caddy flush_interval added + 300s transport timeouts
- Route ordering:
/api/restoredecorator was stacked on backup function → reconnected to restore function - API routing:
/api/restore,/api/backup,/api/lognot proxied → added to Caddy config - Mobile toggle: Inline
display:noneon site tables removed → CSS class toggle now works - Mobile touch: role="button", tabindex="0", Enter key support added to card headers
- Auto-expand first domain: Removed — all domains now start collapsed
- Restore History auto-expanded: tbl-log has class="show", arrow is ▼
Changed
- "Backup Log History" → "Restore History"
- Config page scripts directory now shows content when clicked
2026-07-17 — Initial deployment
- Flask app deployed on app3 as systemd service
- Snapshot script scheduled (1 AM, 1 PM)
- 9 WordPress sites configured for backup
- Caddy proxy from Core via my.itpropartner.com