Before the ‘normal’ DevOpsDays, there was a day filled with workshops. These are the notes of the workshops that I attended.
Articles tagged as “tools”
My browser of choice has been Chromium for quite a while now. A couple of podcasts recently discussed how Chrome has become a memory hog and how Firefox has improved over the years. Time for an experiment.
This is a description of how I created a custom Vagrant box starting from a Lubuntu 14.04 desktop CD.
There are several technologies (in the Python world) to have isolated environments for projects. In this article I will describe how we use Virtualenv, Buildout and Docker for a project I’m working on at Fox-IT.
To introduce a coworker to our project and Django in general, I suggested that he would try PyCharm, a Python IDE. One of the (many) nice things of PyCharm is that you can easily jump to the place where something is declared—ideal for exploring a project.
Since I keep forgetting the name of this monitoring tool, I decided to create an article so I can jog my memory more easily.
Since April 2012 we are using Whiskers to store information about our Plone and Django buildouts. But when I moved the setup behind SSL, the browser started to complain about unsafe content.
Last year I participated in a deployment knowledge sharing session and I started implementing changes at my company pretty soon after. The result is that we are using Puppet for some parts of our server configuration. We also added Munin to our monitoring toolset (and I used Puppet to deploy Munin and manage its configuration). But an important piece that was still missing in our setup was an overview of which packages we use in the buildouts of our clients and more specifically which version each client uses.
A lightning talk by Thijs Jonkman at the Dutch Plone User Day once again brought Compass to my attention. I’ve read about it on other occasions, but I never actually tried it. But Thijs really wet my appetite.