Domain planning
Separate public entry points by responsibility to avoid mixing the application, authentication, and API into one origin.
| Domain | Role | Notes |
|---|---|---|
www.jumpcli.com | Brand entry point | Product overview and public entry point |
app.jumpcli.com | Application | Workspace, account, subscriptions, and operator console |
docs.jumpcli.com | Documentation | VitePress documentation site |
api.jumpcli.com | Developer API | Reserved; open only after API keys, versioning, rate limiting, and separate authentication are ready |
auth.jumpcli.com | Authentication | Casdoor's browser-visible OIDC origin |
static.jumpcli.com | Static assets | May later serve a CDN or public assets |
Reverse-proxy requirements
- Use an HTTPS certificate for every public domain.
- Set the application's
PUBLIC_ORIGINto the actualhttps://app.jumpcli.com. - Include only the actual proxied application hostnames in
ALLOWED_HOSTS. CASDOOR_PUBLIC_ORIGINmust 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.comto the current browser-session application, to avoid confusing Cookie, CSRF Origin, and CORS boundaries.
Initial launch order
- Confirm DNS resolution and TLS certificates are available.
- Publish static documentation at
docs.jumpcli.comfirst. - Publish
app.jumpcli.comand configure its public origin and trusted proxy settings. - Publish
auth.jumpcli.com, then update Casdoor's OIDC callback URL. - 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.