Revision history [back]
Do you mean that /CACHE/ in the file path means it should be coming from the memcached? Actually - it does not. There is no connection between the /CACHE/ directory and the memory object caching (memcached or any other - at all).
Directory /CACHE/ will be created in your static files directory by the django-compressor app. You will need to make sure to make that directory writeable by the webserver.
It's just a directory name. If your site is working with that configuration, that means your memcached is fine.
Do you mean that /CACHE/ in the file path means it should be coming from the memcached? Actually - it does not. There is no connection between the /CACHE/ directory and the memory object caching (memcached or any other - at all).
Directory /CACHE/ will be created in your static files directory by the django-compressorstaticfiles
It's just a directory name. If your site is working with that configuration, that means your memcached is fine.
Do you mean that /CACHE/ in the file path means it should be coming from the memcached? Actually - it does not. There is no connection between the memcached?/CACHE/ directory and the memory object caching (memcached or any other - at all).
Directory /CACHE/ will be created in your static files directory by the staticfiles app. You will need to make sure to make that directory writeable by the webserver.
It's just a directory name. If your site is working with that configuration, that means your memcached is fine.
Do you mean that /CACHE/ in the file path means it should be coming from the memcached?
Directory /CACHE/ will be created in your static files directory by the staticfiles app. You will need to make sure to make that directory writeable by the webserver.
It's just a directory name. If your site is working with that configuration, that means your memcached is fine.