quorlasocial/deploy/provision.env.example
metatroncubeswdev 075b79f6b2 Hosted Quorla: sign-up, Stripe billing, one workspace per agency
- Control centre (QUORLA_CONTROL=true on app.quorlasocial.com): public /signup → Stripe Checkout,
  verified Stripe webhook (paid, updated, cancelled, payment failed), Admin → Agencies
  (approve without Stripe, suspend, resume, billing portal, resend welcome, remove)
- deploy/provision-tenants.sh (cron): one container per agency with its own .env and data,
  nginx map for <agency>.quorlasocial.com, upgrades agencies after a rebuild, archives removed data
- New workspaces: first admin only via the emailed one-time setup link (SETUP_TOKEN)
- Meta system user token can be saved in Settings (encrypted) for workspaces that can't edit .env
- docs/multi-tenant.md: DNS, wildcard cert, nginx, sudoers, cron, Stripe setup; tests for the control centre

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-23 10:35:23 -04:00

10 lines
503 B
Plaintext

# Copy to deploy/provision.env (never commit it). Used by deploy/provision-tenants.sh.
CONTROL_URL=https://app.quorlasocial.com
# Same value as PROVISION_TOKEN in the main app's .env. Generate with: openssl rand -hex 32
PROVISION_TOKEN=
TENANTS_DIR=/home/dev/APPS/quorla-tenants
IMAGE=quorla:latest
TENANT_BASE_DOMAIN=quorlasocial.com
# Settings every agency workspace gets (SMTP for emails; optional shared AI key and platform app keys).
SHARED_ENV=/home/dev/APPS/quorlasocial/deploy/tenant-shared.env