infrastructure

# DigiGrow infrastructure — structural summary

## Two Coolify instances (work-side)

DigiGrow runs TWO Coolify instances side-by-side during the v2 migration:

1. **"New" Coolify** (`atlas-v2-backend`) — primary, hosts the Atlas v2 milestone work and all newer services. SSH alias `digigrow-new`.
2. **"Old" Coolify** — legacy services being migrated off. SSH alias `digigrow-old`.

Both expose REST API v1 with Bearer-token auth. Actual tokens are in `~/.claude/credentials/digigrow-infra.md` (chmod 600).

## Outline wiki — authoritative DigiGrow knowledge base

`https://wiki.admin.digigrow.uk` is the source of truth for ALL internal DigiGrow knowledge (infrastructure, processes, partnerships, sales, marketing). Operating rules:
- Before answering DigiGrow infra/process questions, search the wiki first (`POST /api/documents.search`).
- After meaningful infra changes (new service, DNS change, naming shift, runbook discovery), update the relevant Outline doc — or create one if none exists.
- The "Infra" collection (id `55ed5d1a-bae2-418a-ae42-6c6289fd0c6b`) is the home for everything technical: servers, URLs, DNS, Coolify conventions, service inventory, runbooks, backup strategy, integrations.
- Document tone: written for humans AND future LLM sessions. Headings, tables, fenced code, cross-links, "last reviewed" dates.

## Cloudflare DNS (digigrow zone)

DigiGrow's Cloudflare account owns the `digigrow.uk` and related zones. The account ID and zone IDs are in the credentials file; never expose them in shared surfaces.

## GHL (Go High Level) — CRM

GHL is the CRM source of truth…