How does the Vercel preview environment get the right `DATABASE_URL`? about preview-branches-with-vercel HOT 5 CLOSED

Does the appending DATABASE_URL to .env during migrate get merged with the .env file pulled in with vercel pull

@StevenLangbroek Yes, exactly! That's what this part does.

      - name: Run Prisma Migrate
        run: |
          touch .env
          echo DATABASE_URL=${{ steps.create_branch.outputs.db_url_with_pooler}}/neondb >> .env
          echo DIRECT_DATABASE_URL=${{ steps.create_branch.outputs.db_url}}/neondb >> .env
          npx prisma generate
          npx prisma migrate deploy

I just noticed that this part wasn't explained in the blog post. I'll make sure to update it. :)

Thank you so much for reaching out, and sorry for the delayed response. I didn't get notified when you created the issue :)

from preview-branches-with-vercel.

Awesome, thanks @m-abdelwahab! We should be on production with our first use then early next week 🚀

from preview-branches-with-vercel.

@m-abdelwahab any chance for input from Neon's side? :)

from preview-branches-with-vercel.

No problem @StevenLangbroek! Don't hesitate to reach out if you have any other questions or need help with anything :). You can reach out at [email protected] or DM me on Twitter

from preview-branches-with-vercel.

Hi @m-abdelwahab 👋🏼 Have you tried edge functions with this setup ? From my testing it seems like Vercel functions only pull the preview environment variables from the Vercel dashboard and don't reuse the local environment variables available at build time.

I'm curious if you found a way around that issue. Thanks!

from preview-branches-with-vercel.