We had streamlined the separate views into a single nested view. That works perfectly fine in MySQL, but causes rails db:migrate to choke on a permissions error (at least inside of docker)
We should just go back to the 2 separate views. Otherwise no one can run the migrations (whether automatically in the build or manually by running docker-compose exec backend rails db:migrate)
We had streamlined the separate views into a single nested view. That works perfectly fine in MySQL, but causes rails db:migrate to choke on a permissions error (at least inside of docker)
We should just go back to the 2 separate views. Otherwise no one can run the migrations (whether automatically in the build or manually by running docker-compose exec backend rails db:migrate)