Also, probably disable accessing the database using the writeable user from non-localhost for now, using https://www.postgresql.org/docs/current/auth-pg-hba-conf.html --- this is a defense-in-depth thing.
Why?
It's useful to test the website against (read-only) web data.
There are extremely limited writes from running glados-web. Ideally none. It does run migrations by default, IIRC. If we test glados-web against the prod database, we want to eliminate the chance of accidentally modifying the DB as part of the test, like accidentally running a migration.
Also, probably disable accessing the database using the writeable user from non-localhost for now, using https://www.postgresql.org/docs/current/auth-pg-hba-conf.html --- this is a defense-in-depth thing.
Why?
It's useful to test the website against (read-only) web data.
There are extremely limited writes from running glados-web. Ideally none. It does run migrations by default, IIRC. If we test glados-web against the prod database, we want to eliminate the chance of accidentally modifying the DB as part of the test, like accidentally running a migration.