Skip to content

Host vs Sandbox URL

Two different URLs in orion.config.ts that look similar but serve completely different roles.

Host

Your home tenant — the production-like Orion environment where your developer account and apps live.

Used by:

  • orion login — authenticates you against this tenant.
  • orion publish — uploads your bundle here for marketplace review.
  • orion auth whoami — reads your identity from this tenant.
  • orion apps list / orion apps info — lists the apps you own here.
  • orion versions list / orion versions show — version history for an app on this tenant.

Format: https://{your-tenant-subdomain}.staging.orionsoftware.io.

Set via:

bash
orion config host

Sandbox URL

A scratch tenant used only by orion dev. When you run the local Vite dev server, the CLI opens a Cloudflare tunnel and registers it against the sandbox tenant so the host EMR can iframe your in-progress code without polluting your home tenant's data.

Used by:

  • orion dev — knows which tenant to tunnel into.
  • orion sandbox:status — reports sandbox readiness.
  • orion sandbox:reset — wipes the sandbox back to a fresh state.

Has zero role in login, publish, or any read command. If you don't use orion dev, you can leave it unset.

Set via:

bash
orion config sandbox

Why two?

Same separation as a staging vs production database — except here it's two tenants on the same Orion deployment. Test live-reload code against the sandbox, then publish to the home tenant when you're ready.

Inspect what's set

bash
orion config show

Output:

Current Configuration

  App Name:     my-app
  App Slug:     my-app
  Host:         https://your-tenant.staging.orionsoftware.io
  Sandbox URL:  Not configured
  Tenant UUID:  00000000-0000-0000-0000-000000000000

Documents @orion-ehr/cli v0.0.15 — released under the MIT License.