Skip to content

Domain planning ​

Separate public entry points by responsibility to avoid mixing the application, authentication, and API into one origin.

DomainRoleNotes
www.jumpcli.comBrand entry pointProduct overview and public entry point
app.jumpcli.comApplicationWorkspace, account, subscriptions, and operator console
docs.jumpcli.comDocumentationVitePress documentation site
api.jumpcli.comDeveloper APIReserved; open only after API keys, versioning, rate limiting, and separate authentication are ready
auth.jumpcli.comAuthenticationCasdoor's browser-visible OIDC origin
static.jumpcli.comStatic assetsMay later serve a CDN or public assets

Reverse-proxy requirements ​

  • Use an HTTPS certificate for every public domain.
  • Set the application's PUBLIC_ORIGIN to the actual https://app.jumpcli.com.
  • Include only the actual proxied application hostnames in ALLOWED_HOSTS.
  • CASDOOR_PUBLIC_ORIGIN must match the authentication origin users see in their browsers.
  • Enable trust for forwarded headers only after adding trusted proxy addresses to TRUSTED_PROXY_IPS.
  • Do not reverse-proxy api.jumpcli.com to the current browser-session application, to avoid confusing Cookie, CSRF Origin, and CORS boundaries.

Initial launch order ​

  1. Confirm DNS resolution and TLS certificates are available.
  2. Publish static documentation at docs.jumpcli.com first.
  3. Publish app.jumpcli.com and configure its public origin and trusted proxy settings.
  4. Publish auth.jumpcli.com, then update Casdoor's OIDC callback URL.
  5. Enable real payments only after verifying login, logout, billing connectivity, and payment notifications.

See Production cutover.

Non-public services ​

Meteroid, databases, internal queues, and secret-management services must be reachable only on internal networks. Do not map these services to public ports for debugging convenience.

Local environment ​

Local development may use http://127.0.0.1:9090. Local HTTP differs from production HTTPS in Cookie, security-header, and OIDC callback configuration; recheck them during deployment.

JumpCLI documentation is maintained in a separate repository.