3 ms·
Can you elaborate a bit more on why are you preferring standalone commands instead of going all-ansible? I was considering switch to ansible module for myself b
by pxtail 4y ago
Can you elaborate a bit more on why are you preferring standalone commands instead of going all-ansible?
I was considering switch to ansible module for myself but I'm hesitating, I feel like this could produce quite complex, intricate setup since docker compose itself has many specific stuff like .env files, .env.local files, docker-compose.yml environment specific override files, environment variables and many more so I have mixed feelings when thoughts about intertwining it with ansible arrives.
- nickjj 4y ago> Can you elaborate a bit more on why are you preferring standalone commands instead of going all-ansible? I very strongly believe: - Ansible is a great tool for setting up a server to get it to the point where you can run / deploy applications - Docker Compose is a great tool for running your app - Git is a pretty good tool for initiating deployments In my opinion these are 3 distinct things. Trying to make Ansible do everything gets messy, you also lose feedback. For example if you git push, a post receive hook will stream the response back to your terminal but Ansible will only show output when a task is complete. Using the raw Docker Compose commands also keeps things more consistent between dev, CI and prod. You run basically the same thing in all environments.