Shoehorned content
This post is going to be shoehorned into a hole in my calendar; somehow, yesterday became today without my noticing. Here’s the short (or maybe long) version. The blog stopped working. I waited for a day, and then logged in via the maintenance website. Checked my source code. Grabbed a copy (two, actually) of the database. Called for help in a chat window.
I am impressed by anyone that can repair what seems to be an insurmountable problem, in MINUTES, and then politely excuse taking so long, before checking if I need anything else. I don’t. You just fixed things, you superhero. I had considered, a long time ago, my option of running a personal server. Tried some simple exercises and declared my sanity and time worth whatever the professionals charge (not very much, actually). I’ve been “living” in a server farm ever since. Don’t need to know where. I have the URL.
Yes, I take regular backups, but that’s from professional background. I’ve never had to restore anything. This doesn’t count. What will be posted today (for yesterday) is brand new content, and if I happen across the draft that I (think I) prepared earlier in the week… who cares?
The one good point is that I didn’t break the database (done that one, years ago). This was entirely a configuration error, and nothing I did or said contributed to my glitch. I assume. Anything that you do on a daily basis can seem mundane to others; believe me, it isn’t. I am rather proud of my tenacity.
