mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2025-10-10 10:48:10 +02:00
Kevin Veen-Birkenbach
a817d964e4
- Extract common HTTPS + Cloudflare + handler bootstrap into new role sys-stk-front-base - Update sys-stk-front-proxy, web-svc-cdn, web-svc-file, web-svc-html to depend on sys-stk-front-base - Add new sys-stk-semi-stateless role combining front-base + back-stateless - Update web-svc-coturn to use sys-stk-semi-stateless and rewrite README/meta with detailed Coturn description - Unify sys-util-csp-cert README heading Ref: ChatGPT conversation https://chatgpt.com/share/68d6cea2-3570-800f-acb3-c3277317f17b
14 lines
678 B
Markdown
14 lines
678 B
Markdown
# Semi-Stateless Stack (Front + Back) ⚡
|
|
|
|
## Description
|
|
**sys-stk-semi-stateless** combines the front and back layer into a lightweight, mostly stateless web service stack:
|
|
- Front bootstrap via `sys-stk-front-base` (HTTPS base, optional Cloudflare, handlers)
|
|
- Backend via `sys-stk-back-stateless` (no persistent volumes/DB)
|
|
|
|
Ideal for services that need TLS/front glue but no database (e.g., TURN/STUN, gateways, simple APIs).
|
|
|
|
## Responsibilities
|
|
- Prepare the front layer (HTTPS / handlers / optional Cloudflare)
|
|
- Deploy the stateless backend (typically via Docker Compose)
|
|
- Keep domain variables (`domain`) and app-scoped variables (`application_id`) clearly separated
|