own-proxy decision, terraform provisioner, system diagram, gateway SSE notes, server-budget comment and roadmap 0.4.0 now use Caddy with ACME-managed TLS instead of nginx plus certbot
1.4 KiB
1.4 KiB
Decisions
- Learning contract with PreZero - 2 hours of company time per week plus evenings during a 6-month learning phase; one German one-pager per finished module; the repo goes public.
- v1 scope - What the first public version keeps and what moves to later phases.
- Own Caddy reverse proxy - The apex domain points straight at the home server; a Caddy reverse proxy provisioned by Terraform is the only entry, with automatic HTTPS.
- Provision the server with Terraform - Packages, swap, k3s, Caddy and DNS are Terraform code; workloads inside the cluster stay with kustomize.
- Static Nuxt served by the gateway - Nuxt is generated to static files and embedded in the gateway image instead of running as its own pod.
- Own analytics tracker on SQLite - Analytics are counted by Noel's own code in the gateway and stored as daily totals in SQLite; no third-party tracker, no Postgres.
- CI/CD on Gitea Actions - The existing Gitea instance and runner on the home server build, scan, deploy and version the project.
- Knowledge bundle lives at the repository root - The repository root is the OKF bundle root; any other markdown file there needs frontmatter to stay conformant.
Open
- Open questions - Decisions still to make, with the release that needs each answer.