Re:Docker, Django, Traefik, and IntercoolerJS: My go-to stac...
by paulryanrogers on Sunday January 31, 2021 @11:46AM
(#25980075)
Cost benefit trade offs of Docker will fit some and not others. For smaller projects with less change and few+standard components Docker is probably overkill. In other cases Ansible is too fiddly or slow.
Still important to keep in mind those Docker images must be maintained too.
Re:Docker, Django, Traefik, and IntercoolerJS: My go-to stac...
by hibbelig on Sunday January 31, 2021 @06:15AM
(#25977945)
You can tell Ansible that a package should be removed. You just have to remember to do it. If there was ever a statement in your playbook that a package should be added then you can’t assume it will disappear automatically - you have to tell Ansible to remove it.
Re:Docker, Django, Traefik, and IntercoolerJS: My go-to stac...
by knowhy on Sunday January 31, 2021 @07:25AM
(#25978297)
Most of the stuff you would be doing with Ansible happens inside the Dockerfiles. So comparing lines of code of your Ansible codebase with just the docker-compose file is not fair towards Ansible.
Re:Docker, Django, Traefik, and IntercoolerJS: My go-to stac...
by willemmerson on Sunday January 31, 2021 @10:11AM
(#25979363)
That 100 lines includes the Django docker file which is only 5 lines long, there are no other docker files, at least none I have to worry about.
I don't find docker that useful for developing on a day to dat basis however, it just gets in the way and generally you're not going to need a webserver, SSL, celery, rabbitmq in development anyway. It is useful to debug things locally though.
The other reason to use docker is state: while using ansible we got bitten by old dependencies hanging around because ansible doesn't exactly mirror your config, it can really only add stuff. Whereas docker actually wipes the slate clean every single deploy so your server is an exact mirror of your docker-compose file. This is really important.