Hub provision: public hosted repo
Problem: Paid signup provisions dispatch platform-site-provision.yml on the private marklovely/home-dashboard repo. Every workflow job competes for the single self-hosted lovely-home runner with CI, Terraform validate, auto-merge, deploys, and operator provisions — so hub jobs queue behind unrelated work (~14 minutes vs ~2 on GitHub-hosted).
Direction: A public GitHub repository accepts workflow_dispatch from hub-jobs, checks out the private monorepo with a PAT, and runs the same provision/teardown steps on ubuntu-latest. Registry record / drop jobs stay on the private repo.
Architecture
flowchart LR
Q[HUB_PROVISION_QUEUE] --> HJ[hub-jobs Worker]
HJ -->|USE_LEGACY_VPS_HUB_PROVISION| PRV[private: platform-site-provision.yml on VPS]
HJ -->|default| PUB[public: hub-provision-dispatch.yml]
PUB -->|checkout + PAT| HD[private home-dashboard scripts]
PUB -->|ubuntu-latest| TF[Terraform + provision]
QR[HUB_REGISTRY_QUEUE] --> HJ2[hub-jobs]
HJ2 --> REG[private: platform-site-registry.yml]Phased implementation
Phase 1 — Private repo prep
| Item | Status |
|---|---|
hub-jobs: GITHUB_PROVISION_REPO / GITHUB_PROVISION_WORKFLOW routing for provision + teardown | Done in code |
Terraform optional bindings on lovely-home-hub-jobs | Done (apply separately) |
| Docs: setup guide, public workflow template, secrets sync | Done |
| Tests: dispatch URL / repo selection | Done |
Default (since public orchestrator): Unless USE_LEGACY_VPS_HUB_PROVISION=true on the hub-jobs Worker, provision/teardown dispatch marklovely/lovely-hub-provision (hub-provision-dispatch.yml). Set GITHUB_PROVISION_REPO to override the repo slug. Registry jobs always use PLATFORM_GITHUB_REPO (private).
See hub-provision-orchestrator-ops.md for sync/secrets/deploy checklist.
Terraform apply-platform-admin can set github_provision_repo / Worker bindings from hub.tfvars.
Phase 2 — User creates public repo (manual)
- Create public repo (suggested name:
lovely-hub-provision). - Add
.github/workflows/hub-provision-dispatch.ymlfrom public-repo-workflow-template.yml. - Sync secrets with
--profile provision(see hub-provision-public-repo-setup.md). - Smoke: Actions → Run workflow with
job_action=provision, test site id.
Phase 3 — Flip hub-jobs to public repo (manual + Terraform)
- Set in platform
hub.tfvars:github_provision_repo = "marklovely/lovely-hub-provision"github_provision_workflow = "hub-provision-dispatch.yml"(optional)
- Run Platform admin Terraform →
apply-platform-admin. - Confirm signup provision completes on the public repo Actions tab on
ubuntu-latest.
Rollback: Clear github_provision_repo in tfvars and re-apply, or swap to thin-forward template.
Checklist — public repo secrets (hosted template)
These live on lovely-hub-provision. Values come from hub.tfvars via sync-hub-tfvars-to-github-secrets.mjs --profile provision.
| Secret | Purpose |
|---|---|
HOME_DASHBOARD_REPO | Private repo slug |
HOME_DASHBOARD_REF | Checkout ref (default main) |
HOME_DASHBOARD_DISPATCH_TOKEN | PAT Contents: Read on private repo (legacy secret name HOME_DASHBOARD_CHECKOUT_TOKEN still works in the workflow template) |
| Full provision set | Same names as platform-provision.md (CLOUDFLARE_*, STRIPE_*, TF_STATE_R2_*, PLATFORM_GITHUB_TOKEN, HUB_PROXY_SECRETS_JSON, etc.) |
Thin-forward template only (optional rollback): HOME_DASHBOARD_DISPATCH_TOKEN instead of checkout + full provision set — see public-repo-workflow-template-thin-forward.yml.
Checklist — private repo secrets
Still required for registry workflows, push-to-main auto-provision, and manual provision on the self-hosted runner. Names unchanged; see platform-provision.md.
hub-jobs Worker environment variables
| Variable | Required | Default / legacy | When set |
|---|---|---|---|
PLATFORM_GITHUB_TOKEN | Yes | — | Bearer for all GitHub API calls |
PLATFORM_GITHUB_REPO | No | marklovely/home-dashboard | Registry jobs; legacy provision/teardown |
PLATFORM_GITHUB_REF | No | main | Dispatch ref for all jobs |
GITHUB_PROVISION_REPO | No | marklovely/lovely-hub-provision (unless legacy VPS flag) | Public repo for provision/teardown |
GITHUB_PROVISION_WORKFLOW | No | hub-provision-dispatch.yml | Workflow file in public repo |
USE_LEGACY_VPS_HUB_PROVISION | No | unset → public orchestrator | Set true to dispatch private platform-site-provision.yml on VPS |
Dispatch inputs (public workflow):
| hub-jobs action | job_action | Other inputs |
|---|---|---|
provision | provision | site_id, skip_pages=false, skip_platform_admin=true |
teardown | teardown | site_id |
record / drop | — | Unchanged; always private platform-site-registry.yml |
PAT scopes
Checkout token on public repo (HOME_DASHBOARD_DISPATCH_TOKEN): read private repo contents.
PLATFORM_GITHUB_TOKEN on public repo: write registry snapshots / secrets (same as private provision job).
Hub-jobs token: actions:write on lovely-hub-provision once Phase 3 is enabled.
Related docs
- hub-provision-orchestrator-ops.md — sync workflows, secrets, deploy hub-jobs
- hub-provision-public-repo-setup.md — step-by-step for Phase 2
- public-repo-workflow-template.yml — paste into public repo
- public-repo-workflow-template-thin-forward.yml — legacy VPS forward
- ci-runner-strategy.md — runner queue context