Postgres database errors after merge #318

Closed
opened 2026-04-15 14:25:18 +00:00 by a24timsv · 8 comments
Collaborator

Postgres database errors after the merge and can't store data from middleware.

Postgres database errors after the merge and can't store data from middleware.
Collaborator

postgres started working when i put
"DATABASE_USER=postgres
DATABASE_PASSWORD=AFnRTQac7e4c"

in the .env file

postgres started working when i put "DATABASE_USER=postgres DATABASE_PASSWORD=AFnRTQac7e4c" in the .env file
Collaborator

Is it ok to post password related things in comments? I know this is mockup/prototype thing, but this repo is open to the public so anyone can view it.

Is it ok to post password related things in comments? I know this is mockup/prototype thing, but this repo is open to the public so anyone can view it.
Author
Collaborator

Yeah, the project might be entirely local at the moment but writing password in issues, PRs and the project's files is a bad habit. We were discussing it before we went home today how we are suppose to handle sensitive information, since the password is also in the env.example file.

I'm going to set a standard tomorrow about how we handle password in the project, and we will also change the password since it is public.

Yeah, the project might be entirely local at the moment but writing password in issues, PRs and the project's files is a bad habit. We were discussing it before we went home today how we are suppose to handle sensitive information, since the password is also in the env.example file. I'm going to set a standard tomorrow about how we handle password in the project, and we will also change the password since it is public.
Collaborator

For the fix, I think I does not matter what you put as username and password, as long as the variables are set, since .env is read both for creating the database and for connecting to it

For the fix, I think I does not matter what you put as username and password, as long as the variables are set, since .env is read both for creating the database and for connecting to it
Author
Collaborator

That is true. We have a fix for it at the moment in #326, but we don't want the same password to exist for everyone since it gives the possibility that someone might use that password for a production release in the future. We are discussing right now to modify the scripts to generate a .env file with a random password to avoid this issue.

That is true. We have a fix for it at the moment in #326, but we don't want the same password to exist for everyone since it gives the possibility that someone might use that password for a production release in the future. We are discussing right now to modify the scripts to generate a .env file with a random password to avoid this issue.
b24johka added reference team_1_week_2 2026-04-16 08:26:15 +00:00
Collaborator

This has been resolved in #328 ?

This has been resolved in https://git.webug.se/Andras/BoundlessFlowCampus2K/pulls/328 ?
Author
Collaborator

I haven't checked if #328 solves it, but if you could get it running then it was. Since #326 and #328 was the same error with different scopes both issues solves it. #336 aims to improve the password solution.

I haven't checked if #328 solves it, but if you could get it running then it was. Since #326 and #328 was the same error with different scopes both issues solves it. #336 aims to improve the password solution.
Collaborator

I believe this issue has been solved since the application runs fine, since all related issue's PR where merged.

I believe this issue has been solved since the application runs fine, since all related issue's PR where merged.
Sign in to join this conversation.
No milestone
No project
No assignees
6 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Andras/BoundlessFlowCampus2K#318
No description provided.