Bart Van Geyt 9f819df4d9 Phase 0: architecture docs, ADRs, and repo scaffold

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>

2026-07-07 12:26:00 +02:00

419 B

Raw Blame History

site-templates

Building blocks the provisioning CLI renders from (Phase 3). Empty until then.

Planned contents:

Dockerfiles for standard images: php-fpm (non-root), nginx, static base.
One compose template per profile: static, redirect, custom-php, wordpress — placeholders filled from a site's site.yaml.

Profiles are specified in ../docs/04-site-profiles.md.

419 B Raw Blame History

site-templates

419 B

Raw Blame History