Part V: Keep These Handy (use them when you need them)C
Appendix C
Appendix C: Every human step, and where the keys live
Only the steps your site needs.
Start with the accounts and the local build. Come back for the rows that apply to your site. These are tasks, not a promise that every sign-up takes one click.
Your part, in order
Your clicks, ticked off
0/ 16
Cloudflare upgrades are conditional too. Have the agent explain the plan and expected bill before you approve one.
Where access lives
| Access or secret | Created by | Needed when | Kept where |
|---|---|---|---|
| cf local login | Browser sign-in you approve | Sharing and managing previews | The CLI's credential storage; do not export it |
| GitHub local login | Browser sign-in you approve | Saving the code | GitHub CLI's credential storage |
| Bitwarden access token | You | Extra service secrets | Your computer's keychain |
CLOUDFLARE_DEPLOY_TOKEN | You, scoped with the agent | Optional GitHub Actions | Vault and Actions secret, mapped to CLOUDFLARE_API_TOKEN in the job |
CLOUDFLARE_ACCOUNT_ID | Agent looks it up | Account selection / optional CI | Project config or Actions secret; this is an ID, not a password |
TURNSTILE_SECRET_KEY | Agent | Forms | Worker secret; optional vault backup |
PAYLOAD_SECRET / PAYLOAD_ADMIN_PASSWORD | Agent | CMS | Vault, and Worker secret for PAYLOAD_SECRET |
STRIPE_SECRET_KEY / STRIPE_WEBHOOK_SECRET | You / agent | Store | Vault and Worker secrets; separate test and live environments |
GOOGLE_SERVICE_ACCOUNT_JSON | Agent | Analytics | Vault |
When access expires
Use the relevant browser sign-in again for local access. For a CI token, follow its recorded renewal instructions in Appendix B. Do not create a broad bootstrap token just to fix an expired local login.
On a phone, swipe left and right to turn pages.