saas-multi-tenant.toml RawHistoryFolder

1# Gordon v2 - Multi-Tenant SaaS Configuration Example
2# For SaaS platforms with customer subdomains
3
4[server]
5port = 8080
6registry_port = 5000
7registry_domain = "registry.saas-platform.com" 
8runtime = "auto"  # auto-detects Docker/Podman
9ssl_email = "ops@saas-platform.com"
10data_dir = "/var/lib/gordon"
11
12# Secrets backend for secure credential storage
13[secrets]
14backend = "pass"  # Production should use "pass" or "sops"
15
16[registry_auth]
17enabled = true
18type = "token"  # Token auth for automated deployments
19
20# JWT signing secret (unique to this Gordon instance)
21token_secret = "gordon/saas/token_secret"
22
23# Generate deployment tokens:
24#   gordon auth token generate --subject deploy-bot --scopes push,pull --expiry 0
25# Each Gordon instance has unique tokens (prevents cross-instance token reuse)
26
27# Multi-tenant customer routes
28[routes]
29# Main platform services
30"app.saas-platform.com" = "saas-frontend:v2.1.0"      # Marketing site
31"admin.saas-platform.com" = "saas-admin:v1.5.0"       # Admin dashboard
32"api.saas-platform.com" = "saas-api:v3.2.1"           # Main API
33
34# Customer tenant subdomains
35"acme-corp.saas-platform.com" = "saas-app:v2.1.0"      # Customer: Acme Corp
36"beta-inc.saas-platform.com" = "saas-app:v2.1.0"       # Customer: Beta Inc  
37"gamma-llc.saas-platform.com" = "saas-app:v2.1.0"      # Customer: Gamma LLC
38
39# Enterprise customers with custom domains
40"portal.acme-corp.com" = "saas-app:v2.1.0"             # Acme's custom domain
41"app.beta-inc.com" = "saas-app:v2.1.0"                 # Beta's custom domain
42
43# Staging/testing tenants
44"demo.saas-platform.com" = "saas-app:latest"           # Demo environment
45"staging-tenant.saas-platform.com" = "saas-app:staging" # Staging tests
46
47# Support tools
48"status.saas-platform.com" = "status-page:v1.0.0"      # Status page
49"docs.saas-platform.com" = "documentation:v2.0.0"      # Customer docs
50
51# Multi-tenant deployment strategy:
52# 1. Single application image serves all tenants
53# 2. Tenant identification via subdomain/domain
54# 3. Application handles tenant routing internally
55# 4. Each tenant gets isolated data/configuration
56# 5. Rolling updates deploy to all tenants simultaneously
57#
58# Scaling strategy:
59# - Start with shared containers (same image, tenant routing)
60# - Move to dedicated containers per tenant if needed
61# - Use Gordon's event system for tenant provisioning automation