We use Vercel Hobby for BooksReady, a Next.js application.
We want to verify the effective NEXT_PUBLIC_SUPABASE_URL hostname captured by this existing deployment:
- Deployment:
8jpvCTHg5 - Branch:
preview - Commit:
b370bb7 - Status: Ready
Production and Preview now have separately scoped Supabase environment variables. The current Preview URL points to our intended separate Supabase Preview database, but we want independent confirmation of what this exact deployment uses.
We have checked the deployment settings and metadata. These have not established the deployed URL value. Browser Sources searches found neither supabase.co nor NEXT_PUBLIC_SUPABASE_URL. Authentication runs through server actions, and the deployment Output inspector lists /login as a serverless function without exposing its compiled code.
Is there a supported, read-only dashboard, CLI, or REST API method to confirm only the Supabase hostname captured for this deployment’s build and server runtime?
We want to avoid redeployment, code or configuration changes, application login, database access, or retrieving other environment-variable values. We will not share API keys, tokens, credentials, or database records.
If retrospective verification is unavailable, could you confirm that limitation and recommend the minimum safe verification method for a future Preview deployment?