Skip to content

Document Google OAuth setup for self-hosted deployments - #171

Merged
wasimxyz merged 4 commits into
stagingfrom
wasimxyz/update-docs-20260729
Jul 30, 2026
Merged

Document Google OAuth setup for self-hosted deployments#171
wasimxyz merged 4 commits into
stagingfrom
wasimxyz/update-docs-20260729

Conversation

@wasimxyz

@wasimxyz wasimxyz commented Jul 29, 2026

Copy link
Copy Markdown
Member

Summary

  • Add a Create a Google OAuth client step to first-time deployment, covering consent screen Internal vs External, the fixed /api/auth/callback/google path, and why preview deployments cannot complete Google sign-in.
  • Record that Google is the only gate on who can sign in (ADMIN_EMAILS promotes admins, it does not admit members), and document JWT session design in architecture.md.
  • Fill missing ADMIN_EMAILS and CRON_SECRET rows in the getting-started env table, with cross-links from local development.

Companion docs-site changes: https://github.com/Arcadia-Science/data-hub-docs/pull/16

Test plan

  • Read the new OAuth section in first-time-deployment.md end to end against a fresh Google Cloud project
  • Confirm redirect URI examples match Auth.js Google provider path
  • Check architecture.md JWT/session bullets against current web auth code
  • Verify getting-started env table rows match .env.example / deploy docs

The deploy guide asked for a Google OAuth client without saying how to
create one, and nothing recorded that the consent screen is the only gate
on who can sign in. Add that step to first-time deployment, covering the
fixed callback path, Internal vs External, and why preview deployments
cannot complete Google sign-in.

Also record the JWT session design in architecture.md and add the missing
ADMIN_EMAILS and CRON_SECRET rows to the getting-started env table.

Co-authored-by: Cursor <cursoragent@cursor.com>
@vercel

vercel Bot commented Jul 29, 2026

Copy link
Copy Markdown
Contributor

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
data-hub Ready Ready Preview Jul 30, 2026 6:24am

Request Review

@wasimxyz wasimxyz self-assigned this Jul 29, 2026
Lead with what Data Hub does for a first-time reader rather than how it is
built, and add dashboard, runs-table, and run-detail screenshots so the repo
shows the product. Cover the supported instruments, the web app, REST API, and
MCP surfaces, and `infra/`, none of which the README mentioned.

Replace the quickstart that required `vercel env pull` with the zero-credential
local path, since the old one failed at step three for anyone outside Arcadia.

Stop calling the watcher an agent across the README, `watcher/README.md`, and
the developer docs, now that the word reads as AI agent.

Co-authored-by: Cursor <cursoragent@cursor.com>
@wasimxyz
wasimxyz merged commit a3101c6 into staging Jul 30, 2026
5 checks passed
@wasimxyz
wasimxyz deleted the wasimxyz/update-docs-20260729 branch July 30, 2026 06:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant