Moved three sites to the new hosting environment. Installed Docker for Windows.
Good thing I don’t _need_, like, actual queue workers and stuff.
This web server’s able to deliver email to Gmail, how about that? And with a wrong DKIM record and all. Who needs SMTP?
I don’t _need_ email notifications; most of my WordPress installs push new comment notifications to my RSS reader instead. Guess I’ll stick with Mailgun for the one contact form I still have, just in case.
Hehe. Just went through my spam folder. Mailgun it is. (There’s probably better options, and I don’t want this to become yet another “single point of failure” and so on, but lousy email deliverability, unfortunately, is real—and caused, in part, by the sort of “crappy” shared hosting I’m constantly promoting. 😃)
Although I occasionally dabble in Docker (and use a somewhat proper Valet setup for most of my WordPress stuff), nearly all my “development” consists of just hacking away on “build” sites like this. Later changes mostly happen in VS Code, where I’ll have PHPCS running to clean up things and help me find the most obvious flaws. Most of my “testing” is just that: static analysis/linting, and actually using the things I’m building. And lots of debug logging.
Kinda happy with that workflow, at least for smallish projects—might be why I like to split things up in bite-sized chunks (AKA “abstract away” the real nasty, ugly code in a separate file, class or package).
(Anyway, sites that _work_ ≫ “developer experience,” or dedicated server woes.)
And three more. Four left.
Two left. Might have to upgrade my plan—still going to be a lot more affordable than my previous solution.
All done. Just gotta update DNS records + SSL certs this Monday.
One of ’em suddenly got slow as heck; switched from Redis to file-based caching, all good now. (Shouldn’t it be the other way around? Then again, this is shared hosting, not a VPS, let alone dedicated HW.)