Server Surgery

So, gremlins. I guess that’s what happens with some hard disks. One of them turned a peaceful weekend into a mad scramble for backup space and mdadm tips. Call it a fire drill without the staircases. I guess the server means to say I’ve been taking it for granted. Some lessons learned: You can use drives with different geometry if you have to. An IMPI display would have been very useful for this first-timer.

Test Cycle

So, now that I have this blog updating after changes (i.e. local changes + push to remote), I’m looking to get a little more ambitious. Here are my new requirements for pushing single page apps to my site: An editing model similar to my blog post workflow (see previous post) Pushing to the repository runs tests instead of blindly deploying If tests are successful deploy to host Restart any server processes required Enable dynamic discovery for new apps (i.e.

New Workflow

I’m in the midst of automating deployment of my site using Git hooks. See here for a nice tutorial. There will be other pieces to my ultimate workflow too, such as creating a richer build using grunt and coffeescript, and maybe testing with Jenkins, etc. I’ll probably experiment with these things now that I’ve got my first automated push going. But so far I’m just happy to have a new editing strategy for web site content that works like writing code: Pull site source from repository Add or edit some content (flagged draft) Check it out offline (i.e.

Hello Again

Seems this is a pattern: I get setup with a new blogging engine and I immediately dump a bunch of URLs that have been cluttering up my browser tabs for a couple of days. Some tabs you just can’t close, am I right? What engine, you may ask? Hugo (many thanks to Nate Finch for a great starting point … hope you don’t mind my borrowing your layout). Anyway I’ve already got another one of these undisciplined link lists on my GitHub site (see this post), but I’m keeping a separate one here, kind of off the radar.