Closed dtjanaka closed 2 years ago
Is this for fixing the Database connection error?
ye. related: https://github.com/uclaacm/membership-portal-deployment/pull/2
without these changes, was either getting an error starting the postgres container (would just exit):
postgres_1 | Error: Database is uninitialized and superuser password is not specified.
postgres_1 | You must specify POSTGRES_PASSWORD to a non-empty value for the
postgres_1 | superuser. For example, "-e POSTGRES_PASSWORD=password" on "docker run".
postgres_1 |
postgres_1 | You may also use "POSTGRES_HOST_AUTH_METHOD=trust" to allow all
postgres_1 | connections without a password. This is *not* recommended.
postgres_1 |
postgres_1 | See PostgreSQL documentation about "trust":
postgres_1 | https://www.postgresql.org/docs/current/auth-trust.html
or
would get errors trying to sign in to (or create an account for) the dev membership portal:
postgres_1 | FATAL: password authentication failed for user "postgres"
postgres_1 | DETAIL: Password does not match for user "postgres".
postgres_1 | Connection matched pg_hba.conf line 95: "host all all all md5"
tested on my computers (both Windows/WSL2), @jtsujihara's Macbook (Intel), and @samarthupadhyaya27's Macbook (Intel)
outstanding issue is getting the membership portal working on M1
Is this for fixing the Database connection error?