bart/platform
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
platform/docs/adr
History
Bart Van Geyt e5ff798dd4 Refine to nested customer -> site model 
Adopt a two-level ownership model: a customer owns many sites, with
isolation/containers/DB/backup at the site level and grouping (one SFTP
login, recursive backup, billing, bulk delete) at the customer level.

- 03-naming-conventions: rewritten for customer/site ids and slug =
  <customer>-<site>; nested ZFS, per-customer SFTP chroot, deployments
  mirror the nesting.
- Propagated paths through docs 01, 04, 05, 06, 07 and deployments/README.
- ADR 0005 retitled/updated to per-site datasets nested under customer.
- architecture-plan.md: note pointing to doc 03 as authoritative on naming.

Clarifies subdomains: same-app subdomains are aliases on one site; a
separate-app subdomain is its own isolated site under the same customer.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-07 12:37:39 +02:00
..
0001-single-host-docker-compose.md Phase 0: architecture docs, ADRs, and repo scaffold 2026-07-07 12:26:00 +02:00
0002-traefik-as-edge.md Phase 0: architecture docs, ADRs, and repo scaffold 2026-07-07 12:26:00 +02:00
0003-nginx-fpm-per-site.md Phase 0: architecture docs, ADRs, and repo scaffold 2026-07-07 12:26:00 +02:00
0004-shared-mariadb.md Phase 0: architecture docs, ADRs, and repo scaffold 2026-07-07 12:26:00 +02:00
0005-zfs-per-customer.md Refine to nested customer -> site model 2026-07-07 12:37:39 +02:00
0006-decoupled-backup-streams.md Phase 0: architecture docs, ADRs, and repo scaffold 2026-07-07 12:26:00 +02:00
0007-forgejo-over-gitlab.md Phase 0: architecture docs, ADRs, and repo scaffold 2026-07-07 12:26:00 +02:00
0008-cli-first-panel-later.md Phase 0: architecture docs, ADRs, and repo scaffold 2026-07-07 12:26:00 +02:00
0009-sftp-only.md Phase 0: architecture docs, ADRs, and repo scaffold 2026-07-07 12:26:00 +02:00
README.md Refine to nested customer -> site model 2026-07-07 12:37:39 +02:00

README.md

Architecture Decision Records

Short records capturing why each major choice was made. Format: Context → Decision → Consequences. Status is one of Proposed / Accepted / Superseded.

ADR Decision Status
0001 Single bare-metal host, Docker Compose per customer Accepted
0002 Traefik as the edge router Accepted
0003 Per-site nginx + php-fpm behind Traefik Accepted
0004 Shared MariaDB instance, per-site DB + user Accepted
0005 ZFS dataset per site (nested under customer) Accepted
0006 Decoupled backup streams (files vs DB vs logs) Accepted
0007 Forgejo (lightweight) over GitLab Accepted
0008 CLI/templating first, customer panel later Accepted
0009 SFTP only (no FTP) Accepted

New ADRs are additive and numbered sequentially. To reverse a decision, add a new ADR that supersedes the old one rather than editing history.