Closed frankcollins3 closed 1 year ago
this git issue that's not mine references the code but they are up to doing queries. https://github.com/orgs/vercel/repositories
this issue @ hand has copy-pasted the create-table command from vercel docs.
approach: already checked pages/api page with host:3000/api/graphql which shows the purple apollo server page
[12:21pm]
just missed it on this site a blow flash msg appeared saying: "scope has neon installed. integrate it here" found it from: https://neon.tech/docs/guides/vercel
// blue lower R corner msg went away before screenshot
[12:28pm]
https://neon.tech/docs/guides/vercel:
// dont have ENV_VAR from neon set through vercel. set the neon variables from neon.tech
The integration sets the PGHOST, PGUSER, PGDATABASE, PGPASSWORD, and DATABASE_URL environment variables for your Vercel production, development, and preview environments. Ensure that these variables do not already exist in your Vercel project settings. For more information, see Troubleshoot connection issues.
[12:35pm]
already wondering then why does vercel have: .env.local
and will setting this up through neon specifically to integrate with vercel create .env.local accessibility.
[12:37pm]
👍 might be right:
[12:48pm]
back to vercel issue.
PGHOST 👍 development, preview, production // these words count. Right now I only have the DATABASE_URL filled out.
[12:59pm]
think the mixup is you would do either or. you really wouldn't do native vercel DB calls unless I'm wrong
integrating with another database, you would keep graphQL queries and: just be querying different DB from different connection strings.
[1:16pm]
created tables within neonDB console. now believe the error to be with prisma [1:55pm]
👍 NEXT_PUBLIC_DATABASE_URL 👎 DATABASE_URL [2:02pm]
attempting to do: deploy next with vercel and neon
error: neonDB
proposed approach: reference 08P01 code with vercel docs