Files

T

keyhan bf9e827f85 Add cloudhost-platform Helm chart and registry ingress manifests.

Deploy backend, frontend, PostgreSQL, and Redis on Kubernetes with optional Ingress/TLS, SQL migration hooks, and public registry exposure at repo.3fase.ir.

Co-authored-by: Cursor <cursoragent@cursor.com>

2026-05-24 19:01:05 +03:30

1.1 KiB

Raw Blame History

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).

1.1 KiB Raw Blame History