You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
and I'am using @vercel/postgres. Instead to open a remote DB on Vercel I wanto to use a docker image of postgresDB and connect to it. This is my setup:
.env
# Copy from .env.local on the Vercel dashboard
# https://nextjs.org/learn/dashboard-app/setting-up-your-database#create-a-postgres-database
POSTGRES_URL="postgres://postgres:postgres@localhost:5432/postgres"
POSTGRES_PRISMA_URL="postgres://postgres:postgres@localhost:5432/postgres"
POSTGRES_URL_NON_POOLING="postgres://postgres:postgres@localhost:5432/postgres"
POSTGRES_USER="postgres"
POSTGRES_HOST="localhost"
POSTGRES_PASSWORD="postgres"
POSTGRES_DATABASE="postgres"
Is @vercel/postgres able to connect locally? How can I work locally on my mac without open a remote Database on Vercel.
Additional note: I'am able to connect with other GUI client like TablePlus or AceSql o PGAdmin so my postgress DB docker container is correctly up and running.
Any ideas how to solve?
Thx all
The text was updated successfully, but these errors were encountered:
Hi, I'am trying to follow this tutorial
https://nextjs.org/learn/dashboard-app/setting-up-your-database
and I'am using
@vercel/postgres
. Instead to open a remote DB on Vercel I wanto to use a docker image of postgresDB and connect to it. This is my setup:.env
docker-compose.yml
and my seed file like in tutorial:
https://github.com/vercel/next-learn/blob/main/dashboard/starter-example/scripts/seed.js
the error when I run
node -r dotenv/config ./scripts/seed.js
is:Is
@vercel/postgres
able to connect locally? How can I work locally on my mac without open a remote Database on Vercel.Additional note: I'am able to connect with other GUI client like TablePlus or AceSql o PGAdmin so my postgress DB docker container is correctly up and running.
Any ideas how to solve?
Thx all
The text was updated successfully, but these errors were encountered: