3 ms·
For a single server I’d rather have one config management system - Chef/Ansible/… - and just have that set up docker & nginx, rather than have config management
by jitl 2y ago
For a single server I’d rather have one config management system - Chef/Ansible/… - and just have that set up docker & nginx, rather than have config management set up Kubernetes, and then also need to write Kubernetes manifest YAML files in addition to my config management thingies.
On my home server I use Chef. I have a recipe for each service that sets up a docker container plus an NGINX config that does the TLS and port mapping stuff. To handle container updates I run Watchtower (https://containrrr.dev/watchtower/ https://containrrr.dev/watchtower/) which pulls and then restarts my containers when I send a POST.
Deploys are super easy, just docker build, docker push, curl -h $DEPLOY_TOKEN $DEPLOY_URL.
don’t need anything complicated for rollback, just retag and curl again.
- maccard 2y agoAs I said to the other guy - that configuration had to go somewhere, and for a single server it’s not going to be much. I don’t care if it’s 50 lines of bash, or chef, or yaml. I’d guess that the complexity of configuring find and your services is roughly equivalent to the k8s yaml on a simple setup. It’s a sidestep of complexity IMO.