fresh install: pg-migration don't run and the installation doesn't work

[AxelFooley]

I am using docker with the provide compose file, everything works fine apparently but when i try to login i get a blank page and in the logs i noticed this:

pg_1 | 2023-07-13 07:14:56.063 UTC [95] FATAL: password authentication failed for user "nyala" pg_1 | 2023-07-13 07:14:56.063 UTC [95] DETAIL: Role "nyala" does not exist. pg_1 | Connection matched pg_hba.conf line 100: "host all all all scram-sha-256"

I tried to dig into the code and i've found that this user should be created by this file, but i couldn't find any process actually using it.

Any help will be appreciated.

[gaymersriseup]

This has broken the Docker development environment since 9c7d3553eb018f43ab80d3262fba5b6943eeda86. I despise both Docker and Bash enough that I really don't want to spend time fixing this, but the fix should be simple enough: running the Postgres migrations as a part of web's entrypoint alongside the MySQL ones.

I also don't want to fix this because I don't want to make decisions on how to slot this in with the GitLab CI environment; it looks like the switch from hardcoded credentials for the database to secrets in GitLab CI was intentional, so I wonder if a similar decision (e.g. don't hardcode credentials in the repo) would want to be made here. (I don't really understand why secret credentials for a testing database only spun up in CI is necessary, but that's besides the point I guess.)