Around January, I bought nicholasroth.net to host my experiments and in case I wanted to do anything with it later. Nothing significant happened to the domain until a few days ago, when I heard Google Domains was shutting down, and I transferred nicholasroth.net to Cloudflare.
While I was already in the Cloudflare dashboard, I saw that proxying, rewrite rules, DNS, and more options were available and much more than Google Domains offered. I also already had a laptop connected to my router for storing files, including pulling them from some devices, and running offsite backups. It’s very powerful for the $80 that I paid for it on eBay (broken screen, 12th gen Intel i7), so I figured it might as well also run a blog and anything else I need or want until it gets noisy.
So about a half-day’s worth of work later, I had a docker-compose setup that heavily leans on Cloudflare and I’m frankly surprised by how not-janky it is. This type of configuration would have taken me weeks back in middle school, when the standard was to manually configure Apache. I assume I just have to keep the servers (tags) updated and follow the maintainers’ instructions. MySQL can apparently just accept a previous version’s database directly, and NGINX and certbot should be fairly version-agnostic. That just leaves the WordPress container, whose docs I should probably read before assuming an in-place upgrade will just work like everything else has so far.
I don’t know, I’m probably still missing something important. This is about as far as it gets from machine learning, which is what I actually do for work. My phone also runs Linux. I’ll be talking about that here too :-).
Leave a Reply