exposing postgres to hosts

[Pomax]

Closes #4269 by adding explicit credentials and a host mapping to the docker compose yaml config.

This will keep everything running on 5432 as far as anything inside Docker knows, with docker-new-env updating the .env file with the user/pass/dbname from docker-compose.yml (if set; If not set, they default to the string postgres).

However, postgres is now also accessible on port 5678 from the host OS so that psql postgresql://username:password@localhost:5678/dbname gets you into the Docker-hosted postgres instance, to allow for things like importing a copy of the staging/production db to debug problems associated with real data.

[cadecairos]

Awesome! Ran locally with no issues.

[Pomax]

Of course the one challenge now is to allow for dropdb/createdb, because during a normal docker-compose run, the db is locked due to wagtail being connected to it...

[Pomax]

sorted:

SET ROLE_NAME=......
SET PGPASSWORD=mozilla
pg_dump -F c prodOrStageDATABASE_URL > foundation.db.archive
dropdb -h localhost -p 5678 -U foundation wagtail
createdb -h localhost -p 5678 -U foundation wagtail
createuser -h localhost -p 5678 -U foundation -s $ROLE_NAME
createuser -h localhost -p 5678 -U foundation -s datastudio
pg_restore -d "postgresql://foundation:mozilla@localhost:5678/wagtail" foundation.db.archive

Where ROLE_NAME is the username from the DATABASE_URL

(I have this in a .bat file that is on a completely different drive, in a non-git-managed dir so I can't ever accidentally check it in, with some automated prompts for whether to redownload a db dump, and if so, whether to use staging or prod)