This is a pre-production deployment of Warehouse, however changes made here WILL affect the production instance of PyPI.
Latest Version Dependencies status unknown Test status unknown Test coverage unknown
Project Description

What is it?

This package allows django to purge HTTP cache when a model instance is changed or deleted. It does this by sending “PURGE” requests to one or more upstream HTTP cache (such as Squid or Varnish). This is inspired by Plone CacheFu components.

Usage

In settings.py put ‘django_cachepurge’ before any other application; else it may fail to register some models:

INSTALLED_APPS = (
   'django_cachepurge',
   ...
)

Add the middleware:

MIDDLEWARE_CLASSES = (
    ...
    'django_cachepurge.middleware.CachePurge',
)

Define CACHE_URLS:

CACHE_URLS = 'http://127.0.0.1:3128'

or if you have more than one cache:

CACHE_URLS = ('http://127.0.0.1:3128',
              'http://192.168.1.42:3128')

Models

Urls are extracted from models instances on post_save signal. Two sources are used:

  • instance.get_absolute_url(), if it exists
  • instance.get_purge_urls(), if it exists. The application expects a list of absolute paths similar to what is provided by get_absolute_url().

Purge request is sent when response has been computed: if an exception occurs the urls are not purged. Purge requests are asynchronous: worker threads handle that so that we don’t have wait to complete all requests before returning the response.

Cache configuration

The cache must be configured to accept and handle “PURGE” requests from the server where the django application is hosted.

Contributors

Bertrand Mathieu, Author

Change history

0.3 - 2011-04-01

  • Compatible with Django 1.3: don’t import django.utils.thread_support
  • catch NoReverseMatch exception when trying to find an instance’s url

0.2 - 2010-11-22

  • Accept to purge only site urls, converted if needed into their relative form (i.e, “/some/path/”)

0.1a - 2009-05-25

  • 0.1a: 0.1 released missed some files
  • Initial release
Release History

Release History

0.3

This version

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

0.2

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

0.1a

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

Download Files

Download Files

TODO: Brief introduction on what you do with files - including link to relevant help section.

File Name & Checksum SHA256 Checksum Help Version File Type Upload Date
django-cachepurge-0.3.tar.gz (10.0 kB) Copy SHA256 Checksum SHA256 Source Apr 1, 2011

Supported By

WebFaction WebFaction Technical Writing Elastic Elastic Search Pingdom Pingdom Monitoring Dyn Dyn DNS HPE HPE Development Sentry Sentry Error Logging CloudAMQP CloudAMQP RabbitMQ Heroku Heroku PaaS Kabu Creative Kabu Creative UX & Design Fastly Fastly CDN DigiCert DigiCert EV Certificate Rackspace Rackspace Cloud Servers DreamHost DreamHost Log Hosting