Establish the design foundation for the heleosv2 multi-tenant hosting platform before any implementation code: - Monorepo skeleton: docs/, platform-infra/, site-templates/, deployments/, control-panel/ with orientation READMEs. - docs/: roadmap index, architecture + threat model, naming conventions, site profiles, provisioning workflow, backup & DR runbook, repo/GitOps layout, and the approved architecture plan. - docs/adr/: 9 ADRs recording the rationale for single-host Compose, Traefik edge, nginx+fpm split, shared MariaDB, ZFS-per-customer, decoupled backup streams, Forgejo, CLI-first, and SFTP-only. - Secrets hygiene: .gitignore (only *.enc.* committed) and .gitattributes (LF for scripts/Dockerfiles/YAML run on the Linux host). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| README.md | ||
control-panel
The provisioning CLI (Phase 4), later the customer-facing web panel (Phase 8). Empty until Phase 4.
Planned CLI surface (see ../docs/05-provisioning-workflow.md):
| Command | Action |
|---|---|
provision |
Create a new site end-to-end (ZFS + DB + compose + route + SFTP). |
reconfigure |
Apply changes from an edited site.yaml. |
deprovision |
Tear down a site with gated, backed-up deletion. |
list |
Show all sites, profiles, status. |
backup / restore |
Ad-hoc backup; two-step (files + DB) restore. |
rotate-secret |
Regenerate DB/SFTP credentials. |
Idempotent, declarative (site.yaml is source of truth), logs to Loki.