dip VS bashly

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.

It's heavily inspired by ArgBash (https://argbash.dev/) and uses parts of bashly (https://github.com/DannyBen/bashly/) which are very similar tools :)

Here it's site.

To remove most of the manual things you have to do to make an environment operational, we also use a bash layer on top of Docker. Takes care of initializing of your database, API or any other services for you and puts multiple docker commands under much simpler ones. So even a junior with minimal experience can run it. I use bashly to generate the bash scripts, recommend that useful generator.