Read this first
Start Here
This is the single entry point for bringing Command online without accidentally launching Iridesceux or HVN.
New v20.4 order: get Command's real backend working first. Iridesceux and HVN do not need to be public—or even deployed yet.
The three Command modes
| What you opened | Mode | Meaning |
|---|---|---|
Double-clicked command-app/public/index.html | Offline demo | Browser-only fake data. Safe training copy. |
http://localhost:8788 from Wrangler | Real local backend | Pages Functions run locally. v20.4 no longer forces localhost into demo. |
| Protected Cloudflare URL | Real deployed backend | D1/R2/Access are used. This is the staging/production Command environment. |
Do this in this exact order
1
Read the architecture map
Open Architecture & Folder Map. Do not upload the whole ZIP to one Pages project.
2
Build Command first
Follow First-Time Cloudflare Setup. Create the Command Pages project, D1, Access and bootstrap admin. The public sites can stay offline.
3
Run Setup Doctor
On the deployed Command URL open /setup-doctor.html. It tells you whether Functions, D1 and identity are actually connected.
4
Add R2 before testing uploads
Use D1, R2 & Secrets. Upload buttons require COMMAND_ASSETS.
5
Connect Iridesceux and HVN later
Deploy them as private staging/preview sites when you are ready to test multisite changes. Connecting them does not require public launch.
6
Connect OBS last
Only after Command itself is healthy, follow the broadcast-agent guide.
Do not confuse “Command is deployed” with “the company websites launched.” Command can be online behind Access weeks before the public sites go live.
v20.4 production-readiness audit: the codebase has been hardened and now ships with automated static and backend integration tests. Before public launch, still complete the real Cloudflare staging acceptance test in Production Readiness Tests.
Before staging: read v20.4 Release Audit for the flaws found/fixed and the items that still require real Cloudflare/OBS testing.