keyhan
95d0b162c5
Separate the marketing landing site from the authenticated app by host. Next.js middleware reads PANEL_HOST/LANDING_HOST at runtime and redirects authenticated routes (/dashboard, /login, /register) from the landing host to the panel host, and the landing root on the panel host to /dashboard. Disabled (single-origin) when PANEL_HOST is unset, so local dev is unchanged. Helm: add ingress.panel.host with a third ingress rule + TLS host routing to the frontend service, pass LANDING_HOST/PANEL_HOST to the frontend, and append the panel origin to the backend CORS list (frontend URL stays first so PLATFORM_DOMAIN resolution is unaffected). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
cloudhost-platform
Helm chart for the CloudHost control plane: backend API, frontend UI, PostgreSQL, and Redis.
Quick install
helm upgrade --install cloudhost . \
-n cloudhost --create-namespace \
-f values-production.example.yaml
Ingress / TLS
| Value | Description |
|---|---|
ingress.enabled |
Create Ingress resources |
ingress.tls.enabled |
Enable cert-manager TLS |
ingress.tls.clusterIssuer |
ClusterIssuer name (e.g. letsencrypt-prod) |
ingress.frontend.host |
UI hostname |
ingress.api.host |
API hostname |
Requires NGINX Ingress Controller and cert-manager when TLS is enabled.
Frontend image
Build with the public API URL baked in:
docker build -t $REG/cloudhost-frontend:tag \
--build-arg NEXT_PUBLIC_API_URL=https://api.platform.example.com \
../../frontend
Migrations
SQL files in migrations/ run via a post-install/post-upgrade Job when migrations.enabled is true. They assume incremental schema changes on top of an existing database; for a completely empty database you may need to bootstrap schema first (e.g. one-time NODE_ENV=development or manual setup).