Backend tech points
I worked “.cgi’s” before. In fact, still have one or two of them running on the site. And I’ve worked in Perl, a little later. Then along came “.php” – that’s what the new journal software is written in – that language performs much the same way as the other two – some real geek would argue that, but I’m talking about what I have to do to make the language, or more important, the script, just work. All seems about the same when it comes to twiddling.
I suspect, none of it is much different, not from a programming point of view. Sherman’s Lagoon, a perennial favorite for me, will, at certain times, give me a screen that says “server too busy,” usually, like, first thing in the morning.
So the new software here uses “MySQL” as a database backend for storing all the journal entries. I was considering rolling the scopes into a setup like that, as well, but I’m unsure of how safe, solid, secure and reliable that would arrangement would be.
[img>http://www.astrofish.net/bimages/finally.jpg[/img>The current design and layout of the files’ structure is good for the first ten years of this millennium. No, I haven’t written all of those scopes yet, but the URL expires about the same time I’d have a decade worth of scopes crammed into a tiny archive, all done in HTML format.
The deal is, the way this journal software works is exactly what I’ve been looking for – it does what it’s supposed to do.
That’s what it’s all about, too. More moonlight on the river, headed southward on the pedestrian portion of the First Street Bridge, hooking it homeward Friday night. Most near a full moon, which, in turn, augers well for the weekend fast approaching.
Saturday morning, up and out, off to be an astrologer for the afternoon.
