v260721.02 3:15p
AlpacApps — AI-powered platform with alpacas
Optional pre-setup homework

Create your core accounts first

This is optional. The setup wizard can walk you through these accounts later, but creating them beforehand makes the AlpacApps Infra setup smoother and avoids context switching while Claude is configuring your project.

15–30 minutes before setup

What to prepare

Create or confirm access to the services AlpacApps uses for the basic clone: repository hosting, DNS/infrastructure, database/auth/storage, email, and Google Sign-In.

GitHubSource code, repo access, and static deploy workflow.
CloudflareDNS, Pages, D1 session logging, and R2 storage.
SupabasePostgres database, auth, storage, and edge functions.
ResendTransactional email and optional inbound email webhooks.
Google CloudOAuth app for Google Sign-In through Supabase Auth.
Password ManagerOne secure place for passwords, recovery codes, and API keys.

Keep setup flexible: You do not need to create every project, token, or API key today. Account creation is enough. The wizard will create project-specific resources when it knows your app name, domain, and Supabase project ref.

Save credentials safely first

Use a password manager as the source of truth. A private Google Doc is useful as a checklist, but it should not become the long-term home for passwords, API keys, OAuth secrets, or recovery codes.

Best option: password manager

  1. Use your existing password manager if you already have one.
  2. If you do not, install Bitwarden and create a free account.
  3. Install the browser extension so it can generate and save strong passwords during signup.
  4. Create a folder named AlpacApps Setup.
  5. Add one login item per service: GitHub, Cloudflare, Supabase, Resend, and Google Cloud.

Okay option: private Google Doc

  1. Create a Google Doc named AlpacApps Account Setup.
  2. Set sharing to Restricted, not public or link-access.
  3. Use it for service URLs, usernames, setup status, and notes.
  4. For secrets, write Stored in Bitwarden or the name of your password manager item.
  5. If you temporarily paste a secret there, move it to a password manager and delete it from the doc.

Do not save secrets in public places. Never put passwords, API keys, OAuth client secrets, recovery codes, or database passwords in a public Google Doc, GitHub issue, Slack channel, screenshot, or checked-in repo file.

Copyable credential tracker

Use this in a private doc or as notes inside your password manager. Put actual secret values only in the password manager fields.

AlpacApps Account Setup Project name: Domain, if any: Primary setup email: GitHub - Login URL: https://github.com - Username: - Email: - Password: stored in password manager - 2FA recovery codes: stored in password manager - Notes: Cloudflare - Login URL: https://dash.cloudflare.com - Email: - Account name: - Account ID, if known: - Global API Key: stored in password manager - Domain/zone, if any: - Notes: Supabase - Login URL: https://supabase.com/dashboard - Email: - Organization: - Project ref, if already created: - Database password: stored in password manager - Anon/service keys, if already created: stored in password manager - Notes: Resend - Login URL: https://resend.com - Email: - Domain, if verified: - API key: stored in password manager - Notes: Google Cloud / OAuth - Login URL: https://console.cloud.google.com - Google account: - Project name: - Project ID: - OAuth Client ID: - OAuth Client Secret: stored in password manager - Notes:

GitHub

Free

GitHub hosts your AlpacApps clone and gives Claude/Codex a place to commit and push changes. The setup flow uses GitHub CLI OAuth, so you do not need to create a Personal Access Token beforehand.

Create it

  1. Go to github.com/signup.
  2. Create or sign in to your account.
  3. Verify your email address.
  4. Enable 2FA if GitHub prompts you.

Save it

  • Username
  • Login email
  • Password manager item name
  • 2FA/recovery code location

Cloudflare

Free core

Cloudflare handles DNS, Cloudflare Pages hosting, D1 session logging, and R2 object storage. During setup, Claude uses your Cloudflare email and Global API Key once to create a scoped project token.

Create it

  1. Go to dash.cloudflare.com/sign-up.
  2. Create or sign in to your account.
  3. Verify your email.
  4. If you already own a domain, add it later when the wizard asks.

Save it

Optional ahead of time: In Cloudflare, go to Profile → API Tokens, find Global API Key, click View, and save it in your password manager. The main setup page explains this same step.

Supabase

Free tier

Supabase provides Postgres, auth, storage, and edge functions. It is usually best to create the account now and let the wizard create the project later so the project name, region, and auth URLs line up correctly.

Create it

  1. Go to supabase.com/dashboard/sign-up.
  2. Create or sign in to your account.
  3. Create a free organization if prompted.
  4. Stop there unless you already know your project name and database password.

Save it

  • Supabase login email
  • Organization name
  • Project ref, if already created
  • Database password, if already created

If you pre-create a project: save the database password immediately. Supabase will not show it again, and the setup wizard needs it for database connection validation.

Resend

Free tier

Resend sends transactional email such as welcome emails, booking confirmations, and notifications. You can create the account now and wait to create the API key until Claude is ready to validate it.

Create it

  1. Go to resend.com/signup.
  2. Create or sign in to your account.
  3. Verify your email.
  4. Optional: wait on domain verification until Cloudflare DNS is ready.

Save it

  • Resend login email
  • Domain status, if any
  • API key location: resend.com/api-keys
  • From-address plan, if known

Google Cloud for auth

Free

Google Cloud supplies the OAuth client used by Supabase Auth for "Sign in with Google." Create or choose the Google account that should own login for this app now; finish the OAuth client after Supabase exists so the callback URL and site URL are correct.

Create it

  1. Use the Google account you want to own the app’s login configuration.
  2. Open console.cloud.google.com.
  3. Accept terms if this is your first Google Cloud login.
  4. Optional: create a project at console.cloud.google.com/projectcreate and name it after your app.

Save it

  • Google account email
  • Google Cloud project name
  • Project ID, if created
  • OAuth Client ID and Client Secret, once created and saved in Supabase or a password manager

Usually later: OAuth credentials are easiest after Supabase exists, because the authorized redirect URI will be https://YOUR_PROJECT_REF.supabase.co/auth/v1/callback. The deployed app URL also matters: use https://USERNAME.github.io/REPO/ by default, or https://YOUR_DOMAIN/ if you configured a custom domain.

Ready for the setup wizard

You are ready when you can sign in to GitHub, Cloudflare, Supabase, Resend, and Google Cloud, and you know where the saved credentials live.

What to tell Claude: "I already created the core service accounts. Credentials are saved in my password manager. Continue the AlpacApps Infra setup."

Start AlpacApps Infra setup Open step-by-step guide LLM setup instructions
Infra home Full manual setup guide Sync new features Template repo