4 ms·

There are many reasons why you would want to use Docker but for me the biggest one is that the entire configuration, installation, and deployment is all self-co

by amanzi 8y ago

There are many reasons why you would want to use Docker but for me the biggest one is that the entire configuration, installation, and deployment is all self-contained in that docker-compose file. The rollover and load balancing features are also nice if you need to scale out but even on a single server there is a solid case to be made to use Docker. The alternative you've presented is that you'd need to install and configure Nginx, then install and configure LetsEncrypt, then install and configure Ghost. And then you'd need to make sure you documented all the steps you've performed so that you can do it again if needed in the future. The docker-compose file aligns to the "infrastructure as code" methodology and while there are many other tools that could achieve the same thing (Terraform, Ansible, Salt, etc) using docker-compose in this scenario seems to make sense.

buildme 8y ago
Nothing about using Docker for this makes sense. I’m sick of administrating clever Docker projects because apparently installing nginx on its on (which can easily be done with Ansible or Salt or even a shell script at this point) is too much to ask to host a static website. Those of us who live in Opsland hate maintaining all of these half-baked wheel reinventions.
sneak 8y ago
> There are many reasons why you would want to use Docker but for me the biggest one is that the entire configuration, installation, and deployment is all self-contained in that docker-compose file. Until you write your first blog post or get a single comment. Then you need backups like everyone else who runs their own shit.
codetrotter 8y ago
Installing and configuring Caddy to serve a static site over HTTPS is dead easy, and probably less work than setting up Docker. Caddy has built-in support for Let’s Encrypt. I use the dns module which required a little bit of extra work to enable because it’s not included by default but other than that it’s very simple like I said. Here is the config file for one of my sites: www.crusaders.pw { root /var/www/pw.crusaders.www/ expires { match .htm$ 4h match /assets/.* 1y } tls { dns cloudflare } } crusaders.pw { redir https://www.crusaders.pw{uri} tls { dns cloudflare } } Then just stick the config file in a git repo.
carlopellegrini 8y ago
The fact that everything is done with a single compose file is the reason I set it up like this (mostly because it was a good learning opportunity). I'm still trying to find a way around the necessity to expose the docker socket to configure the proxy though.

by amanzi 8y ago

buildme 8y ago

Nothing about using Docker for this makes sense. I’m sick of administrating clever Docker projects because apparently installing nginx on its on (which can easily be done with Ansible or Salt or even a shell script at this point) is too much to ask to host a static website. Those of us who live in Opsland hate maintaining all of these half-baked wheel reinventions.

sneak 8y ago

> There are many reasons why you would want to use Docker but for me the biggest one is that the entire configuration, installation, and deployment is all self-contained in that docker-compose file. Until you write your first blog post or get a single comment. Then you need backups like everyone else who runs their own shit.

codetrotter 8y ago

Installing and configuring Caddy to serve a static site over HTTPS is dead easy, and probably less work than setting up Docker. Caddy has built-in support for Let’s Encrypt. I use the dns module which required a little bit of extra work to enable because it’s not included by default but other than that it’s very simple like I said. Here is the config file for one of my sites: www.crusaders.pw { root /var/www/pw.crusaders.www/ expires { match .htm$ 4h match /assets/.* 1y } tls { dns cloudflare } } crusaders.pw { redir https://www.crusaders.pw{uri} tls { dns cloudflare } } Then just stick the config file in a git repo.

carlopellegrini 8y ago

The fact that everything is done with a single compose file is the reason I set it up like this (mostly because it was a good learning opportunity). I'm still trying to find a way around the necessity to expose the docker socket to configure the proxy though.