Architecture Decision Records
ADRs explain why a decision was made and what tradeoffs were accepted.
Current ADRs
Section titled “Current ADRs”| ADR | Decision | Status |
|---|---|---|
| ADR-0001 | Use Astro/Starlight for documentation-as-code | Accepted |
| ADR-0002 | Modernize YourBOX with a Symfony 7 strangler pattern | Accepted |
| ADR-0003 | Use PostgreSQL 16 and Meilisearch for the YourBOX data layer | Accepted |
| ADR-0004 | Authenticate YourBOX users through Authentik OIDC with a local fallback | Accepted |
| ADR-0005 | Store YourBOX video assets in Flysystem abstracted object storage | Accepted |
| ADR-0006 | Adopt hexagonal architecture for YourBOX domain layers | Accepted |
| ADR-0007 | Render YourBOX frontend with Twig, Tailwind CSS and Stimulus | Accepted |
| ADR-0008 | Manage YourBOX secrets with SOPS and age in dev, OpenBao and ESO in production | Accepted |
| ADR-0009 | Pin every container image by tag and digest across the workspace | Accepted |
| ADR-0010 | Stage YourBOX deployments across docker compose, Ansible VPS, Azure and k8s | Accepted |
| ADR-0011 | Platform engineering blueprint for the homelab workload plane | Accepted |
| ADR-0012 | Share DevSecOps tooling across application repos through a Copier template | Accepted |
| ADR-0013 | Decide the homelab platform substrate | Proposed |