Skip to content

Collective Setup — Production

This is the production equivalent of Collective Setup — Staging. Read that first; this file covers only what is different for production.

Pre-flight

  • Staging is signed off. The collective, its projects, and the host relationship are all green on staging.opencollective.com.
  • The legacy opsdev-nz project is deleted or archived in the production OpenCollective UI. The dashboard is the only path — oc-opsdevnz has no delete command. (This entry existed before the collective model change; with opsdevnz as a collective, the old flat project is redundant.)
  • opencollective/prod-collectives.yaml exists with prod-appropriate copy of the staging entries.
  • opencollective/prod-projects.yaml no longer lists the legacy opsdev-nz entry.

Promote

Account separation. Staging changes can be made with the everyday john@opsdev.nz delivery account, but production changes require the StartMeUp.nz director account (john@startmeup.nz). The production API token lives in a 1Password private vault accessible only to the director account — the delivery account cannot read it. Sign in as the director before running the commands below.

The commands are similar to the staging runbook, with three differences:

  • Use the production OC_SECRET_REF (op://private/opencollective-prod-automation/token).
  • Drop --staging from every command (prod is the CLI default).
  • Point at the prod-*.yaml files.
eval $(op signin)
export OC_SECRET_REF="op://private/opencollective-prod-automation/token"

# Verify auth and host
oc-opsdevnz whoami startmeup-nz

# Create the collective and apply to host
oc-opsdevnz collectives --file opencollective/prod-collectives.yaml

# Create the projects under the collective
oc-opsdevnz projects --file opencollective/prod-projects.yaml

Verify

Open https://opencollective.com/opsdevnz and confirm: fiscal host badge, name, description, tags, and projects are all in place.