4 ms·
I don't think docker-compose will ever be dead, it's the easiest way to setup a local environment that needs one (db?) or more (db and queue?) components. Deplo
by atmosx 6y ago
I don't think docker-compose will ever be dead, it's the easiest way to setup a local environment that needs one (db?) or more (db and queue?) components. Deploying locally to k8s (minikube) takes still some time (build the image, push it to the local registry, run the deployment manifests, etc.) which become a PITA for very small changes.
I prefer to run DBs using docker and docker-compose on my homeLab linux servers than installing MySQL through the package manager. A lot cleaner/easier/faster to configure.
- ahpearce 6y agoI've been doing this a lot lately as well. It's just really easy to have a directory of compose scripts in your home dir, and setup a simple bash alias/func to stand up a quick database.
- dmarlow 6y agoThis! I prefer to define various docker-compose files wrapped with a makefile. Then, spin up various parts of the project with simple commands like `make api-up` It's so easy and simple, I don't know how I ever lived without it. So much is supported, I feel like it's so easy to get everyone on a team on the same page without having to install and configure so many different things. Funny enough, despite all of these containers, I actually don't deploy any to actually run any of the code or dependecies. It's all just for the ease and speed of development.
- cnimativ 6y agoI think that's the disconnect between docker-compose and ops. It's really easy to setup the dev env, but there's no direct way yet of deploying docker-compose stack somewhere w/o wrangling/writing a bunch of yml files using different libraries...