Via

I'd love this!

This would de-anonymize the user (obviously, in this hypothetical scenario that's not a bad thing), thus making "anonymous" an inaccurate descriptor.. There are many reasons a user may want to...

Getting this error as well - external server url was redacted :) ``` client_1 | 2022/07/27 21:02:31 [error] 10#10: *19 connect() failed (113: Host is unreachable) while connecting to upstream,...

My docker compose does not appear to have a password or user, it appears I was definitely meant to create one, that would be tremendously useful to have in the...

It appears docker has it's own postgress image - of which I have no idea how to access, and I have no clue if this image is what is being...

> This should only happen if you change the POSTGRES_PASSWORD after the database has been initialized (in MOUNT_SQL). An easy fix would be to either change the password back to...

I've reverted any changes I made to docker_compose.yml - I only started looking there after I had trouble with the current config My MOUNT_SQL appears to be correct (I don't...

Here's my full .env without the password ``` # Database credentials POSTGRES_USER=szuru POSTGRES_PASSWORD=secure password definitely not 1234 # This shows up on the homescreen, indicating build information BUILD_INFO=latest # Port...

> > I may have initially had the wrong password (default) under `#Database credentials` in `.env`, could this be causing an issue? I've re-ran `docker-compose pull` and `docker-compose up -d`...

> > I may have initially had the wrong password (default) under `#Database credentials` in `.env`, could this be causing an issue? I've re-ran `docker-compose pull` and `docker-compose up -d`...