CMS Client Config

Sign in to manage customer deployments.

Customers

Customer profiles are separate from deployed instances.

Customer ID Name Email Phone Updated
Loading...

New Customer

Applications

Select an application definition, then deploy an instance for a customer.

New Application

Source and image registry settings

These settings override server environment defaults for this application.

Verify settings checks the entered values without saving or deploying.

Instances

Application instances are read from GitOps overlays.

Instance Customer App Version Name Last Updated URL VPS IP
Loading...

Edit Instance

Runtime secrets are stored in Kubernetes Secrets and are not read back from Git.

Manifest Files

Command Log

New Instance

VPS

Optional. Paste the wg-easy client config for this VPS when central ArgoCD must reach the customer K3s API over VPN.

Central ArgoCD is the only supported deployment mode. Use the edge WireGuard IP here when the VPS is behind NAT.

Instance

App Image verified ✗

App Ingress Configuration

Choose public IP for direct DNS to Traefik. Choose private IP when the edge server is behind a router and needs Cloudflare Tunnel.

Create this DNS record manually at your DNS provider, then verify it here.

App Ingress Configuration verified ✗

MongoDB

Admin Bootstrap

SMTP

Provider presets use TLS/STARTTLS on port 587. Host, port, and security are locked after selecting a provider.

Registry

Leave these blank to use configured server-side GHCR credentials.

Application Secrets

Complete each required wizard stage first. App Ingress Configuration must be verified before publishing.

Final Verification

Run this after publishing. It verifies the public app URL, edge Traefik routing, and frontend/backend services. If CMS_Client_Config applied the tenant directly, central ArgoCD reachability is reported as advisory.