mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-26 01:06:00 +03:00
[GH-ISSUE #3217] [bug]: Error when running pnpm exec prisma migrate deploy #1060
Labels
No labels
CodeDay
a11y
browser limited
bug
bug fix
cli
core
critical
design
desktop
discussion
docker
documentation
duplicate
enterprise
feature
feature
fosshack
future
good first issue
hacktoberfest
help wanted
i18n
invalid
major
minor
need information
need testing
not applicable to hoppscotch
not reproducible
pull-request
question
refactor
resolved
sandbox
self-host
spam
stale
testmu
wip
wont fix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hoppscotch#1060
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @galaxy78r on GitHub (Jul 27, 2023).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3217
Is there an existing issue for this?
Current behavior
I am trying to install selfhosted hoppscotch
I am using the default database that is provided with the docker container and after building the image when I run the commands
docker ps # copy the id of hoppscotch-backenddocker exec -it id bashpnpm exec prisma migrate deployI get the error :
Error: P1001: Can't reach database server at
hoppscotch-db:5432Please make sure your database server is running at
hoppscotch-db:5432.Thanks you in advance for your support
Steps to reproduce
git clone https://github.com/hoppscotch/hoppscotch.git
Copy the contents of .env.example file found in the root directory of cloned repository to .env and add your own values for the environment variables.
pnpm install
docker compose build
docker ps # copy the id of hoppscotch-backend
docker exec -it id bash
pnpm exec prisma migrate deploy
Environment
Production
Version
Cloud
@galaxy78r commented on GitHub (Jul 27, 2023):
Issue was solved by running
docker compose up