rails VS dip

Since I mostly dealt with Active Record and Action Cable, my Docker configuration wasn't complete. Also, back in the days, the Rails codebase wasn't container-friendly (e.g., some tests relied on a Redis or PostgreSQL instance running on the same machine). Thus, I just kept my setup around (in a few commits], and haven't tried to promote to the upstream or whatever.

And then also add dip to get rid of these lengthy docker compose run prefixes from the every command typed in your console.

So, I went the old-fashioned way and added Dip to the mix. Now I can run all the familiar commands (bundle, rake, etc.) from my host system (with a dip prefix) without thinking about all the docker-compose --rm --it bla-bla. Moreover, I can cd into a subfolder (say, actioncable), and execute commands from there just like on a host machine:

And in this case this utility can safe us. DIP has two possible modes:

I'd be sure to also check out (if you haven't already) https://evilmartians.com/chronicles/ruby-on-whales-docker-for-ruby-rails-development, it might have some solutions to your problems, like using a cached Docker volume to mount your application's directory. Evil Martians also developed DIP to help make the Docker workflow more approachable.