Dev dump

[bamader]

Mount a pg_dump extract to docker dev

Summary

This PR creates a .sql dump of the PG database just after the eRSD has successfully been loaded via a local docker compose run. It has been mounted into the docker dev volume to automatically run as an entrypoint script when running in dev mode.

Related Issue

Fixes #122

Additional Information

Added a readme with the command needed to create the dump file in case we ever want to update the dev dump. Code tested by nuking all images, docker system pruneing, then just running npm run dev and verifying values were in the DB via DBeaver.

[m-goggins]

Looks good! I believe we need to mount the same volume to the db docker-compose-e2e so that the data is available for end to end tests.

[bamader]

Actually that reminds me that we need to also call the valueset insertion functions for the DIBBs hardcoded values / JSON dump file that you wrote at /src/app/assets/DIBBS_Custom_ValueSets.json in the create DB functions overall. This dump doesn't include those so our e2e's will totally fail. I'll update the code and the dump mount.

[robertandremitchell]

makes sense to me. I wonder if we actually want to commit the vs_dump.sql to github or just have it locally? or do we need to upload it for tests to pass successfully?

[bamader]

@robertandremitchell I believe we'll need to upload it for tests to pass once we take the migrations out. I'll have to modify the github workflow to take advantage of it. I think it's also probably good to commit it in case anyone else needs to pull things down and be able to iterate quickly, e.g. a designer who wants to test out a new feature's appearance.