Public network site
Running the HVN Website
HVN is public, but its market presentation, player state, ads, CMS changes and analytics are controlled from Command.
Normal website content change
- Command → Site Studio.
- Switch the site selector to HVN.
- Edit the approved safe field.
- Preview on a test page/market.
- Publish.
HVN Pages deployment settings
Framework preset: None
Build command: exit 0
Root directory: hvn-site
Build output directory: public
Keep hvn-site/functions/ at the project root and hvn-site/public/ as the static output. Use a private staging/preview deployment before attaching the production HVN domain.
Live player / presentation data path
Command→D1 state→HVN /api/hvn/*→viewer presentation runtime
HVN's public viewer endpoints must remain publicly readable where the player needs them. Do not put the entire HVN domain behind Access.
Before changing live HVN
- Confirm the correct market tab.
- Use PREVIEW/CUE before TAKE where available.
- Confirm the Program Monitor matches the expected market.
- Keep a tested backup feed and standby loop ready.
- Use KILL ALL GRAPHICS only when necessary.
Staging monitor note: v20.4 allows the Command monitor to frame approved HVN production/staging origins. Test the actual Command → HVN preview before launch. If you do not need wildcard
*.pages.dev staging framing later, tighten the HVN frame-ancestors policy to the exact staging/production Command hosts.v20.4 runtime connections
- Schedule: the live schedule now reads non-draft HVN blocks from Command/D1 through
/api/hvn/schedule. Static W3Schools/MDN demo video sources were removed; if the schedule API is unavailable the page fails closed to “Schedule unavailable.” - Viewer accounts: HVNid registration/login/profile/location/watchlist now have real Pages Functions. Follow HVN Viewer Accountsv20.4 Release Audit.
- Presentation: station IDs/bugs, butterfly, loop, ads, breaks and safety remain driven by the HVN control API/presentation runtime.