I’ve been using Gatsby for the better part of this year to host my blog. I get a nice static blog that can become interactive relatively easily. Unfortunately, I think the JS ecosystem is moving a bit too quickly for me to maintain with all my other commitments. So I’m going to swap that maintenance headache for another 🙂 and move to WordPress.
Over the coming months, I’m going to be moving my blog to WordPress. As time permits, I’ll be detailing my progress here. My initial conception is a simple stack with a cheap CDN in front of my WordPress instance in a reproducible setup so I can work offline when needed.
I expect to learn a lot about the broader container ecosystem and will be paying close attention to CNCF publications and videos. Expect the page size to go down and the performance to stay around the same. I’ll also be working on my PHP knowledge to add back in interactivity to this site.
Two main goals: (1) create a setup I can quickly replicate locally and on different cloud providers; and (2) learn more than I can handle about the Kubernetes “revolution.”
Initially, this will only host my WordPress blog (the future of this blog).
A late goal is some time of notification system when new builds are pushed.
I’ve landed on the following stack:
- Kubernetes, to control spinning up and down of virtual machines. We’ll force k8s to use a single machine.
- Vagrant, to build and manage the virtual machine environment. It also abstracts the available hypervisors on different operating systems.
- Ansible, to prep the container which will head into the container registry.
- minikube for testing locally
- VMWare Fusion for running virtual machines.