There’s many situations where success is preceded by pain, or at least arduous strain. Breaking loose that rusted bolt on your project car, cramming for your final exams, debugging production issues at 2am, running a marathon. Sometimes the success is worth the pain. Sometimes the pain is inevitable. Sometimes there is no success at the end of the pain. But is the pain necessary for success?
What if there were a magical universal pipeline compiler that could take any project and create a functional, beautiful pipeline for any CI provider to cover the basics, and allow infrastructure-independent enhancements by developers?
After quite some time, I’ve finally released the v1.0.0 of cheesy-gallery, a new jekyll photo gallery. You can see some examples at this site using it.
For one of the webpages I’m responsible for, I’m tracking traffic through Google Analytics. One of the things that really irked me was a massive distortion in the data through traffic that was not very natural to the eye. Looking for its details found a few posts across the web complaining about similar bot traffic, but no solution that worked for me. Since the start of September, this traffic has…
Picking up where I left off almost 8 months ago, I started working with the cheesy-gallery source today. Over the last couple of days I’ve mostly updated and cleaned up the Gemfile and travis-ci configuration while re-familiarising me with the project.
Over the last couple of months I’ve been slowly building out my home office. Between that and the push to even more home office over the next months and Puppet instructing folks to take their chairs and monitors home, I’ve considerably upgraded my working situation at home. This post describes the current statue of the setup, and what works and doesn’t work.
Today, a change of pace: getting 52GB of image files synced with git-annex in a way that still provides for a nice editing/publishing workflow and keeps history for blogposts around.