starred/planka
1
0
Fork 0
mirror of https://github.com/plankanban/planka.git synced 2026-02-25 03:14:50 +03:00
Code Issues 396 Packages Projects Releases 16 Wiki Activity

'Role "ghostly" does not exist' error during database initialization #142

New Issue
Closed
opened 2026-02-04 17:29:28 +03:00 by OVERLORD · 2 comments
OVERLORD commented 2026-02-04 17:29:28 +03:00
Owner
Copy Link

Originally created by @egglessness on GitHub (Nov 22, 2021).

Hi folks! First and foremost, thank you for sharing this awesome project!

I'm trying to set up a development instance, but unfortunately I'm unable to get the database working.

I've started the postgres container using docker-compose -f docker-compose.dev.yml, but when I run the npm run server:db:init command, the app crashes saying: error: role "ghostly" does not exist.
The same error message appears in the log from postgres: FATAL: role "ghostly" does not exist.

As far as I understand, the apps seems to be able to talk with the db container, but the authentication fails.

Is there anything that I'm missing?

Originally created by @egglessness on GitHub (Nov 22, 2021). Hi folks! First and foremost, thank you for sharing this awesome project! I'm trying to set up a development instance, but unfortunately I'm unable to get the database working. I've started the postgres container using `docker-compose -f docker-compose.dev.yml`, but when I run the `npm run server:db:init` command, the app crashes saying: `error: role "ghostly" does not exist`. The same error message appears in the log from postgres: `FATAL: role "ghostly" does not exist`. As far as I understand, the apps seems to be able to talk with the db container, but the authentication fails. Is there anything that I'm missing?
OVERLORD commented 2026-02-04 17:29:46 +03:00
Author
Owner
Copy Link

@meltyshev commented on GitHub (Nov 22, 2021):

Hi! Oops, I forgot to change the user in the .env file after local development. I will fix it in the next commit.

@meltyshev commented on GitHub (Nov 22, 2021): Hi! Oops, I forgot to change the user in the .env file after local development. I will fix it in the next commit.
OVERLORD commented 2026-02-04 17:29:51 +03:00
Author
Owner
Copy Link

@egglessness commented on GitHub (Nov 22, 2021):

Yes! Just found out that the DATABASE_URL variable in the server/.env file must be set as follows:

DATABASE_URL=postgresql://postgres@localhost/planka
@egglessness commented on GitHub (Nov 22, 2021): Yes! Just found out that the `DATABASE_URL` variable in the `server/.env` file must be set as follows: ``` DATABASE_URL=postgresql://postgres@localhost/planka ```
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
bug
documentation
documentation
duplicate
enhancement
good first issue
help wanted
pull-request
Mirrored from GitHub Pull Request
 question
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/planka#142
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?