Skip to main content

cubicweb varnish helper

Project description


This cubes enables a purge mechanism for a cubicweb website that is sitting behind a varnish cache.


The purge mechanism consists of sending purge commands to the administration backend of varnish (by default localhost:6082). Generally it is recommended to protect this management port with a secret file which can be configured in this cube. Multiple backends can be controlled in this manner in a distributed setup.

Out of the box, this cube will not purge any URLs. The logic of which pages should be “purged” has to be implemented in content cubes.

To configure which urls to purge, you have to implement an IVarnishAdapter, for example

.. sourcecode:: python

from cubes.varnish.entities import IVarnishAdapter

class BlogEntryVarnishAdapter(IVarnishAdapter):

__select__ = is_instance(‘BlogEntry’)

def urls_to_purge(self):
return (‘/’, #frontpage
self.entity.absolute_url(), #URL of blog post ‘/BlogEntry’ # list of blog entries)

Debugging : cubicweb-varnish will not crash when it cannot connect to the administrative port, it will silently log an error in the log.


or apt-get install varnish (for debian derived distributions)

Project details

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Filename, size & hash SHA256 hash help File type Python version Upload date
cubicweb-varnish-0.4.1.tar.gz (6.6 kB) Copy SHA256 hash SHA256 Source None

Supported by

Elastic Elastic Search Pingdom Pingdom Monitoring Google Google BigQuery Sentry Sentry Error logging AWS AWS Cloud computing DataDog DataDog Monitoring Fastly Fastly CDN SignalFx SignalFx Supporter DigiCert DigiCert EV certificate StatusPage StatusPage Status page