This is a short follow-up article to the NAS TLS certificate replacement one I wrote a few months back. Since then I have set up monitoring of the TLS certificates I’ve deployed.
All Day DevOps is an online conference which lasts for 24 hours. With 150 sessions across 5 tracks, there’s enough content to consume.
Microsoft Ignite | The Tour: Amsterdam is a two day tech conference organized by Microsoft. On this first day I attended the talks in the “Building your application for the cloud” learning path.
The first day of the Open Source Summit Europe 2018.
As I mentioned last month, I enjoyed working with Visual Studio Code when I used it to create my devopsdays notes. I even started using it for my day-to-day work four weeks ago. And I still like it!
The second, and last, day of talks of devopsdays in Amsterdam this year.
These are my notes of my second day at DockerCon.
These are my notes of my first day at DockerCon.
For a project I am working on, there is this virtual machine we can use to do our development work in. This machine has grown organically and I want to replace it with something I can reproduce. I wanted to experiment with Packer but had problems with generating a machine with two network adapters where the second one is connected to a host-only network.
Shell scripts I come across sometimes have for instance “
#!/bin/bash -eux” on the first line. Because I’ve Googled for this too many times
now, I’ll record the meaning of these options here for my own sanity.
Before the regular DevOpsDays kicked off, there was a day filled with workshops.
My notes from the second day of DevOpsDays Amsterdam 2016.
My notes from the first day of DevOpsDays Amsterdam 2016.
Before the ‘normal’ DevOpsDays, there was a day filled with workshops. These are the notes of the workshops that I attended.
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 post 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 made me want to try it for myself.
Initially I was a bit sceptic about Fabric. After all, I’m already using buildout to manage projects. “How much better can it get?” After watching the video of the Django Deployment Workshop (held by Jacob Kaplan-Moss at PyCon 2010 Atlanta), I finally decided to see for myself what Fabric is all about.
Google’s Webmaster Tools provide the modern webmaster/developer with some nice tools to improve a website and the way the site is indexed. In this article I’ll focus on the crawler related tools. Specifically, how they helped me when I migrated from Plone to Django.
The summary: as of today, you no longer need to checkout
enablesettrace from the Zope Subversion repository. You can just use
the Products.enablesettrace egg to debug your restricted Python code.
On 19 February I held a presentation for my colleagues about distributed version control systems (DVCS). My main goal was to inform them on what I think is the next logical step in source control.
I frequently have to send emails from web applications. But before I deploy to a production environment, I want to make sure the mechanism works and the right mails are constructed. Here’s two ways to do that.
This blog entry is about a real life example of how the flexibility of Git made my life easier. It’s a story about how I stopped developing a feature halfway to try out an alternative, without throwing away anything or cluttering up the (Subversion) repository.
While I’m enthusiastic about Git, I still have to communicate with Subversion repositories like the Plone Collective. I also like my editor (Emacs) to help me interact with Git. In this blog entry I’ll explain how I setup my work environment.
A talk about working with packages, zc.buildout and managing the application lifecycle.
Setuptools doesn’t seem to like subversion 1.5.