Hi @michielbdejong, I found this, which seems to be our problem: https://stackoverflow.com/questions/39135919/docker-compose-rails-rake-dbreset-fails-cannot-drop-the-currently-open-databa

TL;DR -- the fact that our development database was named postgres was creating conflicts

I renamed it to phoenix_development, but you'll have to run docker-compose build to incorporate the changes.

Also, you'll need to create the phoenix_development database via the postgres container db and psql. When you exec into the container, make sure you're going in as the postgres user: docker exec -ti -u postgres db bash.

I'd be interested in automating that step.

If you still run into problems with db:reset, try these one after the other: db:drop db:create db:migrate db:seed

Not super related, but there's also a rake task for creating the document types: docker exec -ti edittosdrorg_web_1 bundle exec rake document_types:create_document_types

I can work this into the seed, if preferable?

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud