docs(okf): replace Cloudflare Tunnel with own nginx reverse proxy

direction change: own nginx proxy (Terraform-installed, certbot TLS) is the only public entry; add own-proxy decision; update system, gateway SSE notes, server budget and accepted-downtime docs
This commit is contained in:
Noel Sabia committed 2026-10-14 21:54:33 +02:00
1 parent e432895080
commit 3636053a35
8 files changed
+47 -14

No files matched your search

+28
View File
@@ -0,0 +1,28 @@
---
type: Decision
title: Own nginx reverse proxy instead of Cloudflare Tunnel
description: The apex domain points straight at the home server; an nginx reverse proxy installed by Terraform is the only entry.
tags: [decision, networking, nginx, terraform]
status: stable
generated: { by: claude-code/claude-opus-5-5, at: 2026-10-14T00:00:00Z }
verified: { by: human:noel, at: 2026-10-14T00:00:00Z }
---
# Decision
No tunnel, no managed entry service. A DNS A record points the apex domain at
the home server directly; nginx (installed and configured by Terraform, with a
certbot certificate) terminates TLS and forwards to the gateway Service.
# Why
- A managed tunnel outsources exactly the part Noel wants to learn: DNS, TLS,
proxies and what happens between a browser and a container.
- No dependency on a third party. The entry path is Noel's own code and config.
- nginx on the same 4 GB server costs a few MB, well inside the budget.
# Consequences
Inbound ports 80 and 443 must be reachable at the home server (router
port-forward, static IP or DDNS). This is a solved-but-open question — see
[open questions](/decisions/open-questions.md).