It’s no exaggeration to say that the internet has gone through tremendous changes since its birth three decades ago. In particular, the UI/UX space has undergone some drastic iterations, with the explosion of many different devices, screen sizes and their accompanying demands. To meet the needs of users across screens and devices, it’s more important than ever that we constantly improve our applications to ensure that regardless of device, users can still easily access and use the web application. And we cannot ignore that fact that things are still changing, and we need to keep learning and update in an ongoing way to provide better user experiences to our end users.
It’s not new, but when people start using Varnish Administration Console (VAC), we often get questions about user access roles in the VAC. We covered this in our blog when we originally set up three distinct access roles - but it never hurts to offer up a refresher.
Varnish Administration Console 3.3.0 is now available
We're happy to announce a new version of the Varnish Administration Console (VAC). This is a maintenance version which includes some bug fixes. We recommend that you upgrade your existing installation.
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.