System map
Architecture & Folder Map
Know exactly what each folder does before deploying anything. The most common deployment mistake is uploading the entire bundle as one website.
Production architecture
Viewer→Iridesceux / HVN public Pages↔D1 + R2←Command private Pages←Cloudflare Access
Command Master Control→Broadcast Agent→OBS WebSocket localhost→Stream
Folder map
| Folder | Purpose | Deploy? |
|---|---|---|
public-site/ | Iridesceux Pages project root. Static site is public/; Functions stay in functions/. | Yes → root public-site, output public |
hvn-site/ | HVN Pages project root. Static/player files are public/; Functions stay in functions/. | Yes → root hvn-site, output public |
command-app/ | Private Command Pages project root. Static app is public/; Functions stay in functions/. | Yes → root command-app, output public, behind Access |
broadcast-agent/ | Trusted local service that talks to OBS. | Run on broadcast PC/server; do not serve publicly |
hvn-realtime-worker/ | Optional faster realtime graphics wake-ups. | Optional Worker |
hvn-safety-worker/ | Optional scheduled safety/weather ingestion. | Optional Worker |
DOCUMENTATION/ | Canonical private manuals. | Never on public sites |
offline-command-demo/ | Local visual demonstration. | No |
Never: upload the complete package root to
iridesceux.com or HVN. That can expose internal files, backup source, documentation, and server configuration.