Org infra
Strategic "which vendor" guidance lives in the capability areas. Org infra answers how this org’s stacks encode DNS and shared platform resources.
Articles (bootstrap path)
-
Back up Pulumi stack state —
stack export, object-storage backends, Drive offline copies, rclone GUIs -
Transfer a project into an org — personal accounts cannot join a Cloud Identity org; bridge with an org account holding Project Mover on the organization
Background in General Knowledge
Canonical explanation pages — linked, not duplicated here:
-
Org infra repo pattern — Pulumi TypeScript + Antora docs layout
-
Pulumi Cloud org model — free Individual cannot invite; Organizations are paid or self-hosted state
-
Pulumi secrets vs stack state — encrypted config in git ≠ resource inventory backend
Room to grow
Future pages: hostname conventions (updates., cal., vault.), apply/preview habits shared across orgs, ESC as secrets distribution hub.
Member-only hostnames
Static sister docs (Antora) stay static. Put Cloudflare Access on the orange-cloud hostname and on *.pages.dev. Reader identities are GitHub org membership (or Google / email PIN) — not Cloudflare dashboard users. Access asks GitHub at login (GET /user/orgs); it does not keep a member roster.
Interconnect
-
Forge identity (profile / site / docs hub) before this repo exists → Fast org bootstrap
-
Email DNS roles → Email
-
Personal Gmail / Routing limits → Personal Gmail send-as gotchas
-
Booking / design / vault hostnames → Scheduling, Design, Vault
-
Developer IaC mechanics → Infrastructure as Code
-
Reference lookup → Technology → Infrastructure