The example you give has 6 config files.... the linked article uses 1 config file. shrug
The example you give has 6 config files.... the linked article uses 1 config file. shrug
Since when does X[1] support system-wide configuration/deployment?
But yea, when using Docker already, why not? It's quick and easy compared to all the alternatives.
EDIT: Others are already expressing my point, that this is overkill for a blog.
You can still use a CDN in front of a very tiny VM. Some new blog engines even support running on serverless/FaaS platforms for every easier deployments, and once FaaS evolves into just running Docker containers then the circle will complete and we'll have the best of everything.
Really, you don't even need Ansible.
Just ssh into the box, apt install nginx, run the Let's Encrypt script and install Ghost.
But, sure, you could do it in a more complicated way, or a more manual and time consuming way that isn't documented or automated. I think that's called the "job security" method.
Shouldn't we also be using k8s to orchestrate all the blogs?
That heavily depends on if this is a "learn new tech" thing or not. Some people view setting up a blog as a challenge to solve, and some people just want a blog up and running so they can write. And if this does it in a simple to follow guide that is reliable, the tech behind it doesn't really matter.