Finishing setup

Five steps. Until step 2 is done the registry stays in its holding state and shows no data to anyone.

1. Create the Google sign-in credentials

  1. Open the Google Cloud console, pick the Diiiploy project, and go to APIs & Services → Credentials.
  2. Choose Create credentials → OAuth client ID, application type Web application, and name it “Pages Registry”.
  3. Under Authorized JavaScript origins add:
    https://pages.diiiploy.io
  4. Under Authorized redirect URIs add:
    https://pages.diiiploy.io/api/auth/callback/google
    For local work also add http://localhost:3000/api/auth/callback/google.
  5. On the OAuth consent screen, set the user type to Internal so only diiiploy.io accounts can even reach the prompt.

2. Put the credentials into Vercel

Add GOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRET to the project’s environment variables for Production, then redeploy. The registry switches out of setup mode on the next deploy.

3. Point the address at it

DNS for diiiploy.io is edited in Squarespace, not Vercel. Add the record Vercel asks for on the domain screen:

DNS usually settles within minutes; Vercel issues the certificate automatically once it resolves.

4. Create the tables

Apply the repo's migrations from a checkout (per platform standards — schema changes ship as migrations, never hand-run SQL): supabase link --project-ref rdscvkhmabgvakbsrwjw then supabase db push. The 0002_seed migration grants admin to chase@diiiploy.io and trevor@diiiploy.io and creates the five starting access groups. (Already applied for this deployment on 2026-09-05.)

5. Turn on the email alerts

Set RESEND_API_KEY in Vercel. Until it is set, the sync still runs and still catalogs new pages — it just does not send the “new page” email, and it leaves those pages queued so they are emailed once the key exists.

How it runs after that