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
Did you check to see if this issue already exists?
Is this only a feature request? Do not put multiple feature requests in one issue.
Is this a backend issue? Use the lemmy-ui repo for UI / frontend issues.
Is your proposal related to a problem?
During startup of the lemmy containers, if postgres isn't ready to accept connections yet lemmy will log the failed attempt and include username/password in that log.
Log files may have less stringent permissions, whilst the postgres password itself is part of a docker secret.
Example: Error connecting to postgres://lemmy:PASSWORDHERE@lemmy-postgres:5432/lemmy: connection to server at "lemmy-postgres" (172.21.2.3), port 5432 failed: FATAL: the database system is not yet accepting connections
Describe the solution you'd like.
Replace the password with a single "x", or some other suitable subtitute.
If required, an additional environment label could be used to re-enable credentials in logs, although I wouldn't recommend it.
Describe alternatives you've considered.
.
Additional context
No response
The text was updated successfully, but these errors were encountered:
Requirements
Is your proposal related to a problem?
During startup of the lemmy containers, if postgres isn't ready to accept connections yet lemmy will log the failed attempt and include username/password in that log.
Log files may have less stringent permissions, whilst the postgres password itself is part of a docker secret.
Example:
Error connecting to postgres://lemmy:PASSWORDHERE@lemmy-postgres:5432/lemmy: connection to server at "lemmy-postgres" (172.21.2.3), port 5432 failed: FATAL: the database system is not yet accepting connections
Describe the solution you'd like.
Replace the password with a single "x", or some other suitable subtitute.
If required, an additional environment label could be used to re-enable credentials in logs, although I wouldn't recommend it.
Describe alternatives you've considered.
.
Additional context
No response
The text was updated successfully, but these errors were encountered: