📚 HospAir Documentation
Everything beyond the main README, organised by who you are.
| Guide | Read it if you… |
|---|---|
| OPERATIONS.md | run the station day to day: studio use, deploys, troubleshooting, backups |
| NGINX-PROXY.md | are putting a server on the internet: the TLS edge, ports, firewall |
| CLOUDFLARE-DNS.md | manage DNS: studio / listen / live / connect records |
| roadmap.md | want the product story: every phase shipped and planned |
| liquidsoap-roadmap.md | hack on the playout engine: pull-queue architecture, Liquidsoap 2.4 thread-safety findings, delivery plan |
🏁 Production checklist
- NGINX-PROXY.md: set
.envhostnames, thendocker compose -f docker-compose.yml -f docker-compose.prod.yml up -d --build - CLOUDFLARE-DNS.md: three proxied records + one DNS-only for the encoder
- OPERATIONS.md: sign in, check streams, configure BUTT, schedule backups
⚠️ Before touching the playout engine
Read the thread-safety section of liquidsoap-roadmap.md first. On Liquidsoap 2.4.x, mutating or even inspecting source state from outside the clock thread can silently take the station off air, the engine's design rules exist because we hit every one of those failure modes the hard way.