When I left for work I thought that I had the whole site up and running in a manner that, while far from perfect, was at least adequate. Functional. Lo, my dismay: when I went to make the first welcoming post featured below this one, I was met ultimately with an unpleasant message:
500 Internal Server Error
For whatever (probably diligent and wholly security-minded) reason, my place of occupation does not permit SSH connections. So no shell into the server for Josh. So no fixing the problem. So eight torturous hours of ignoring some glaring and site-paralyzing bug preventing me from making that cathartic First Post to justify the long weekend spent coding and debugging and cursing and annoying my wife.
It was a pretty stupid bug, too. Not even a bug. A permissions issue. A minor oversight in the workflow of a utility script that, in theory, I’ll never even have to run again.
It’s fixed now, though, because (and this is one of the key lessons I have learned as a programmer, one of those truisms of coding that should be written in a tiny black notebook of programmatical koans to be pondered by students of the arcane arts) at some point I will again run that script that I think I’ll never have to run again.
Anyway, welcome to the site. Soon, I can bury all this ridiculous “the site is new” omphalaskepsis in actual posts about actual things.