view the rest of the comments
Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
First of all, make sure the PostgreSQL username matches as well.
Does your password contain any special characters such as quotes, dollar signs or backslashes? They can have special meanings in yaml, resulting in the password being different from what you'd expect.
Username definitely matches!
And yes, I have several special characters, but the password is surrounded by single quotes in
docker-compose.yml
, so that should not matter, right?At the very least, dollar signs will still matter, due to environment variable interpolation.
This makes sense, and I do have a dollar sign in my password...
However, I have confirmed that postgres does in fact parse the password correctly, as I can log in with the defined username/password combo directly using
psql
So I think that disproves this theory, doesn't it?
edit: I tried getting rid of the dollar sign just in case... unfortunately I'm still getting the same error