Maintenance
See Framework → Maintenance Services for what each of these categories is and why it matters. This page is which tool was actually picked for each, and where its setup is documented.
| Concern | Function | Tool | Status | Notes |
|---|---|---|---|---|
| Deployment | Deployment platform | Coolify | ✅ Running | Setup: System → Coolify |
| CI/CD | — | Not evaluated | Forgejo Actions is the obvious candidate given code hosting is already Forgejo, but nothing's been evaluated yet | |
| Development | Code hosting | Forgejo | ✅ Running | Hosts this site's own source |
| Security | Password manager | Proton Pass | ✅ Running | The one deliberately non-self-hosted piece of this stack |
| Credential manager | Infisical | Not adopted, low priority | Proton Pass already covers this; self-hosting a credential manager reopens its own backup/recovery problem, not worth the added complexity right now | |
| Auth / IDP | Authentik | ✅ Running | Setup and known issues documented there | |
| Monitoring | Stats | Beszel | ✅ Running | |
| Status pages | Uptime Kuma | ⏳ Not deployed | ||
| Error tracking / APM | — | Not evaluated | Monitors individual apps, not the platform — last for that reason | |
| Backups | Disaster (off-site) | Backrest | ⏳ Not deployed | |
| Operational (local snapshot) | OpenStack Snapshot Scheduler | 🔧 Not built | Custom, unbuilt |
Credential setup for provisioning tooling itself is in Infrastructure → Infrastructure as Code. Credentials generated once things are actually running go to Proton Pass.