Hopefully, the same. Over the weekend, I migrated my web site from a brand-x hosting service to a DIY server hosted by Amazon Web Services (AWS). After the disappearance of my site last spring, I’ve been looking for an excuse to find it a new home, but didn’t want to spend a lot of time fussing with the details of site management and migration. Turns out (as so many things do), it was much easier than I anticipated. The migration was straightforward and accomplished in just a short time, once I knew what I wanted to do.
AWS offers a dizzying array of configuration options, which can be very intimidating to the weekend webmaster. So, the first problem was to figure out which server options I wanted to use (i.e. pay for). I opted for tiny, which seems to work well enough. Being virtual servers, I can always level-up (or down) if performance becomes an issue. In all fairness, the hardest part was trying to figure out what I really wanted.
Once I got the server running to my satisfaction, Step-by-Step Guide to Migrate Your WordPress Site to a New Host provided the details to migrate the site contents (files and database tables). The hardest part of that process was realizing that I needed to create an .htaccess file on the new server.
Going through a Cloudflare load balancer made switching to the new server as easy as typing in the IP address of the new server. A couple of summers ago, I moved the public IP of my site to Cloudflare to take advantage of their SSL support. That gave my site its padlock (finally) and a bunch of other features–like the presto-chango IP address. No DNS records involved at all. Best of all, if I messed something up, I just type in the old server’s IP until I get things sorted out.
So, this is my first post of the new year (2020…and I still upset that don’t have a flying car that I was promised in the 1960s views of the 21st century). And, my first post on the site’s new server.
Happy and prosperous new year!