Skip to content

Conversation

@wil
Copy link

@wil wil commented Oct 29, 2010

Hi David,

I fixed a test case (believe it was a regression due to the os.path.realpath commit), and also pulled the CACHE_BACKEND feature from django_compressor (with test), and would love to have these included so I don't have to keep this fork.

The cache backend feature is essential for my use case because I'd like the default Django cache backend to use a shared cache of multiple memcached instances, but when running Django on multiple machines, django-css will find that the compressed file path is already in cache (placed by another Django instance on a different machine) and it won't bother to generated the media file locally causing a 404. Obviously this can be solved by some sort of NFS or using a storage backend that is distributed, but we intentionally do not want that.

Let me know if you have any questions or concerns.

.wil

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant