Posts
My home, automated
Posted on (read in 3 minutes)
Given that I work in the technology sector, it should be no surprise that I have an interest in home automation. I’ve toyed with it on and off for years, but finally seem to be making progress with a system that actually does what I want. In this post, I’m hoping to kick start a series of posts that document my journey and setup with home automation. Currently, that entails my Home Assistant-based hub and all the devices it integrates together.
HTTPS Only
Posted on (read in 1 minutes)
I have finally joined the twenty-first century and made this website HTTPS only. This is supposedly good for Google ranking and it is definitely good for privacy. All non-HTTPS requests are now redirected to HTTPS. Further, I’ve implemented HSTS, disabled SSLv2 and SSLv3, and done all of the things necessary to get an A+ on SSL Labs. Hooray for security! The next step will be supporting HTTP 2.0.
Website changes, again
Posted on (read in 2 minutes)
A few years have passed so it seemed like it was time for yet another website change. I’ve not changed much visually, but I’ve changed the entire static content generation stack. Previously, my site was generated using a static content generator called Nanoc. It took a set of source files written in Markdown, HTML, Haml, Sass, and a bunch of other stuff and output them as HTML and CSS. I had a lot of complexity.
Migrating VMs to a new vSphere cluster
Posted on (read in 3 minutes)
Where I work, we use VMware to virtualize the majority of our servers. Last year, we bought four new servers in order to provide more resources to our virtual evironment, and also to aid in the upgrade to vSphere 4 from VI3. The plan was to power off all virtual machines and perform an offline migration of all the VMs from the old cluster to the new cluster. However, we were also migrating from the vSwitch to the distributed virtual switch (dvSwitch).
A New ${HOME}
Posted on (read in 2 minutes)
Up until last week, this website was run on a generic shared hosting account. For the most part, this worked well. At times, it could be slow. I went through all kinds of trouble to tune WordPress as much as I could to make it respond faster. Unfortunately, a lot of the slowness was in the shared MySQL server that they provided. I had them move me between servers a few times, but it never fully resolved the issues.