Tag: Site Meta

Posting about the website and/or webserver.

  • A Hot Mess Of A Site

    Yes, I’m tinkering again. Now that I know how to make a 2-column layout in WordPress Twenty Twenty Five, I have done so. Too bad all the older stuff I used to rely upon is dead. (I mean, yes, technically I could force “classic” widgets and layouts… but for how much longer? Probably not very.)

    I’m not 100% happy with it yet but at least I have the calendar and links back, even if I have to do the links “by hand” because having the link categories configured in WordPress itself is absolutely obsolete now. Progress. Or something.

    Also, the sidebar RSS widget for bringing in my “fediverse” content won’t be coming back because the “new” widget looks awful and can’t be customized the way I need it.

    At this point I’m tempted to jump ship from WP but… I still want to be self-hosted, and what else is out there which isn’t too minimalist, is widely supported and rich with features, and will run on OpenLiteSpeed? Ha ha. Fun times.

  • The (al)Lure of Static Site Generators

    So, with all the argy-bargy in the news about WordPress and the guy in charge of it and the ecosystem being affected by that guy’s shenanigans… why stay on WordPress? Why not, for instance, jump on the bandwagon of the last few years and change over to a static site generator (or SSG)? This site could load much faster, and with vastly less server processing overhead! No more SQL database, no more finicky plugin shenanigans… easy peasy, right?

    I spent most of my morning today reading up on doing exactly this, and while it might still work for the webcomic (provided I never update it again… which is admittedly all-too-likely) it won’t work here, and it took hours of reading before I finally found someone who pointed out why:

    When you update the site, you have to regenerate every page on the site. Every time. A lot of these guys (and it’s all guys, yes) have maybe a couple dozen posts, tops. Regenerating the flat files from Markdown sources could take them maybe a minute or so! Who cares, right?

    The current count of entries listed as “posts” on the website you’re reading right now is well over 2,500. And that’s not counting “pages” and other such additions.

    Yeah, nope. I can’t take that seriously. I want to be posting here more often, not less. And if I find myself dreading the rebuild time every time I want to publish, that’s not going to help. (Never mind if something about one of those several thousand posts breaks the generator!) So if I migrate off of Dubya Pee it’ll have to be to something more… CMS-y.

    Such is the way of things, I suppose.

  • Another New Look: 2025

    Things look a bit odd over here, don’t they? No two-column layout, no randomized header image (yet, maybe).

    Here’s the thing: Hemingway was a very good website theme, I liked most everything about it, but it’s long in the tooth and was eventually going to become fully obsolete. The inevitable march of technology, or something. So upon the advice of professional website designers, I’m… using the new Twenty Twenty Five default WordPress theme.

    (And yes, using WordPress is a fraught choice in and of itself nowadays, for certain reasons we’re not going into at the moment. At least I’m self-hosted.)

    I have a lot of fiddling and fussing to do, so expect things to look a bit odd for a while. Or, like, forever, depending.

    Wish me luck making sense of this bold new scheme.

  • Dream A Little Dreamwidth Me

    I know, I’ve been quiet again this month. I think I’m still adjusting to being in the house and having the ability to completely relax in my own home. I have some plans, some tentative and one much less so, for things to do here. (If you think the less-tentative plan involves a particular video game… well, you’re 100% right.)

    March 7 from Honkai Star Rail is unimpressed. I don’t really blame her.

    But in the meantime I’m also doing things over at… Dreamwidth. I mean, not directly because I’m crafting this post in the WordPress editor. But I’m resuming cross-posting to DW because… well, why not? I still have a few friends on DW and they’re not following the not-a-blog. And it’s not like I post so often that I’m going to overwhelm either site with “content.”

    So… let’s try this out (again) and see how it goes.

  • Duo Universal

    Just a quick heads-up for other WordPress admin types who installed the Duo plugin years ago and kind of forgot about it… apparently it’s been deprecated in favor of a new plugin which supports the new “universal prompt” system. It’s not hard to upgrade (deactivate old, install new, activate new, enter the same token/passkey/hostname as you did before into new, authenticate, delete the old once you’ve confirmed new works) but I wish there’d been a bit more communication about this.

    Also be aware that Universal Prompt defaults to an immediate push notification rather than giving you a button to click to initiate a push. Other than that, it’s basically the same, and works just fine. Hooray for security.

  • Migration Yet Again

    It’s amusing to look back on previous server migration posts and realize how long I’ve been a Linode (now Akamai, oh boy) customer. And yet, only a couple of years after the last round of server changes I decided to do it once again.

    Why?

    Mainly because I wanted to get away from the Apache webserver. While it’s the workhorse driving a lot of the World Wide Web even now, it’s showing its age and, well, there’s the whole naming optics thing, isn’t there? And after seeing an online friend rave happily about this thing called OpenLiteSpeed (including how much less of a pain in the backside it is to deal with versus NGINX, the other leading option) I figured, you know what? It’s time for a change.

    So change I have. This site, along with nearly all of my other web-based projects, lives on yet another new Linode/Akamai virtual server, this time without the usual Apache webserver setup. My thoughts on “OLS” itself will have to percolate a bit before I can craft them into a coherent post but in short: It’s quite slick, but its documentation has some glaring holes and it isn’t always easy to search online for fixes to weird problems. Additionally, certain WordPress plugins don’t like it very much. (Or OLS doesn’t like them. Take your pick.)

    It is downright peppy, though, and a breeze to administer. Setting up the reverse proxy for my Foundry VTT rig was actually simpler than it had been under Apache… not that OLS’ documentation made that any easier to figure out, mind you.

    I still have some things to move over before shutting down ‘node3’ but considering I only spun up the new host Saturday morning, to be here midday on Tuesday with nearly everything sorted and settled? I’m happy with this result, yeah.