Postgres database errors after merge #318
Labels
No labels
_CRITICAL_
API
app
backEnd
Blocked, waiting for further changes
bug
cleanup
close
design
duplicate
enhancement
feature request
frontEnd
help wanted
invalid
low priority
needs input
needs review
project documentation
question
research
reviewed
script
security
SQL
style
testing
topLevel
wontfix
No milestone
No project
No assignees
6 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Andras/BoundlessFlowCampus2K#318
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?
Postgres database errors after the merge and can't store data from middleware.
postgres started working when i put
"DATABASE_USER=postgres
DATABASE_PASSWORD=AFnRTQac7e4c"
in the .env file
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.
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.
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
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.
This has been resolved in #328 ?
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 believe this issue has been solved since the application runs fine, since all related issue's PR where merged.