Steps to improve development scenario

[kevin-meyers]

Disconnect from the proxy Create a docker image to host a local psql (and write some seed data that gets pulled in on image create) Start printing my migrations to a folder somewhere and a script to handle applying them to production

Needs breaking into issues

[kevin-meyers]

Yesod (and more specifically, Persistent) has migration support. There's a section on migrations in the Persistent chapter of the Yesod Book: https://www.yesodweb.com/book/persistent#persistent_migrations For development, it's fine to let Yesod perform the migrations for you. For deploying to production, I strongly recommend only printing the migrations (which is just a matter of using the printMigration function instead of the runMigration function). In order to actually trigger the migrations, one thing we've done in the past is make a little command line executable in addition to the main webserver executable (requires defining another executable section in your .cabal file) that is compiled/executed separately. If your project is called "foobar", you may produce a foobar-server and a foobar-cli, the latter of which can take args to toggle between running migrations in development mode and printing migrations for

[kevin-meyers]

Dockerfile set up successfully! Remaining tasks:

• [ ] Add postgres db image and connect it
• [ ] Remove all traces of keter >:(
• [ ] Add the code locations (like src/ and some config/) to volumes: in the docker-compose so it can live update.
• [ ] Maybe make sure there are no more data-dictionaries and are all data-scout
• [ ] Start printing migrations instead of running them, so I can manually run them in production (maybe I can still let it auto apply on local?)
• [ ] disconnect from proxy
• [ ] start setting up terraform with ECR (refer to messages with Jeff)