HVN Site Operations

Staging/deployment, market verification, legal redirects, graphics architecture, and player-operational checks.

Deploy HVN staging

Create the HVN Pages project

Workers & Pages

Connect the same private repository.

Set build configuration

HVN project

Root directory

hvn-site

Framework

None

Build command

exit 0

Output

public

Expected: HVN *.pages.dev staging URL loads.

Bind shared resources

HVN project → Settings → Bindings

Bind COMMAND_DB and COMMAND_ASSETS if the current Functions use shared Command state/media. Add optional HVN_ANALYTICS only when Analytics Engine is actually configured.

Set optional realtime URL

HVN project → Variables

If the realtime Worker is deployed, set HVN_REALTIME_URL to its public subscriber origin.

Redeploy after bindings/variables

HVN project → Deployments

Use a deployment created after the configuration changes.

HVN staging verification

Open and test these routes/functions on staging:

/hvn_website.html
/hvn_live_streaming.html
/api/hvn/config
/api/hvn/control?market=new-york
/privacy-policy.html   # should redirect to Iridesceux legal/privacy destination

Then switch through all six markets: New York, Chicago, Philadelphia, Seattle, San Antonio, Miami, plus National. Verify each market identity/presentation state behaves as expected.

Market architecture

National

Common network feed/presentation state. National bumper may be baked into program master.

New York

Local market identity + station ID/bug + eligible local ads/alerts.

Chicago