We have already established that managing several Varnish instance(s) and keeping the configuration coherent between them can be difficult. Part one of this blog series covers this pretty well. Monitoring and deploying configuration, restarting the instances in a synchronized fashion requires some knowledge. The Varnish Administration Console (VAC) provides a full API that will help make this a whole lot easier.

Here in the second post of this series, we'll show you how to do VCL change management and continuous integration using the VAC API and Git.

folks are already hacking away in @ben_hall's tutorial on @docker #security and performance models today at #OSCON pic.twitter.com/6w1Puah6pv

— loro inc (@loro_inc) May 19, 2016

OSCON was a blast! I can't compare it to other conventions since it's my first, but the organization was a very well-oiled machine and it really allowed everyone - exhibitors and visitors alike - to really focus on the heart of this event: Open Source. Being invited by GitHub (thanks Jono, Brian and the whole team), we were located in a pretty central booth at the Open Source Alley, where we had to handle a lot of traffic (but that's cool, we're Varnish, we know how to handle that).

...and a little #OSCON booths #3 w/ @github because awesome booth! pic.twitter.com/iVh2TYpw39

— Λdrøn (@adron) July 22, 2015