Architecture Decision Records

Architecture Decision Records (ADRs) document the key technical choices made in this platform, the context that drove them, and their consequences.

What is an ADR?

An ADR is a short document that captures a significant architectural decision. Each ADR describes:

• Status — proposed, accepted, deprecated, or superseded
• Context — the situation that called for a decision
• Decision — what was decided
• Consequences — the trade-offs and outcomes

Records

ADR	Title	Status
001	Containerize with nginx Alpine	Accepted
002	Private Images via GHCR	Accepted
003	Self-host Umami Analytics	Accepted
004	GHCR Push with SHA Tagging	Accepted
005	K3s on Azure Spot with Cloudflare CDN	Accepted
006	Observability with Grafana, Loki, Promtail	Accepted
007	PostgreSQL on Azure Flexible Server	Superseded
008	Infrastructure as Code with Terraform	Accepted
009	CI/CD with GitHub Actions and Flux	Accepted
010	ACR Primary, Retain GHCR	Accepted
011	Git Hooks with Husky and lint-staged	Accepted
012	Developer Secret Management	Accepted
013	Monorepo with pnpm Workspaces	Accepted
014	Migrate Spot to On-demand B2s	Accepted
015	Origin TLS Certificate Management	Accepted
016	Second K3s Node for Observability	Accepted
017	Managed PostgreSQL as Shared Database	Accepted