Every now and then I spin up a small CA for a service. I’m doing it for OpenVPN, internal https traffic, even for my sensu instance. As I expected, this technique works just fine with Docker as well. My tool of choice is easyrsa. The tool itself is not rocket science, but it’s well structured, easy to use, and it’s versatile. Let me show you around.
Recently it crossed our mind we need a monitoring solution. For a background, we’re running a team for maintaining a couple of applications, but the OS-level support is done by another team.
ruby 2.0.0 has been released, I wanted to use it. I have built
it the day after on my notebook, but it took more than two times as much time
to run all the specs for my recent rails project, than with
falcon-gc. I’m certainly getting the wrong results, don’t I? Sure I
do. Yesterday I grabbed my pickaxe, to dig out the root of the problem.
I’m very happy to be a git user. I really am. Being a ClearCase admin, I’m even more. This time I wanted to split out a small part of my puppetmaster config, but I also wanted to keep it there as is.
The newest drama club activities aim overtesting. DHH has placed his coin telling one should not try to have 100% coverage.
I spent most of my career in chairs. I sat beside various sizes of tables. One thing never changed though: their heights.
I decided I give rbenv a shot. This change also means I have to find another way to separate rails gems from my standard ones. I’ll tell you why.
Back to basics, you might think. When I started blogging, I wrote my own engine in PHP. It was a breeze to use, it had modules and styles (called flavours), and blog posts could be written as files. However, it was not a content generator engine, since it picked up these text files on every hit.