Opened 7 years ago
Closed 7 years ago
#28614 closed Cleanup/optimization (wontfix)
FileBasedCache documentation shouldn't recommend /var/tmp
| Reported by: | Daniel Keller | Owned by: | nobody |
|---|---|---|---|
| Component: | Documentation | Version: | 1.11 |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
In the documentation for django.core.cache.backends.filebased.FileBasedCache, it suggests putting the cache in /var/tmp, presumably because it is world-writeable. However, this causes major headaches if you run Apache with systemd's PrivateTmp feature (PrivateTmp is on by default in REHL) and try to access the cache from e.g. management commands. This is useful to do things like periodically prepopulate the cache. A better choice would be /var/cache.
Change History (2)
comment:1 by , 7 years ago
comment:2 by , 7 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
Feel free to respond to my comment if you disagree with it.
Note:
See TracTickets
for help on using tickets.
On my machine,
/var/cacheisn't world-writable. I'm not sure if it's worth the extra hassle of requiring the user to create a directory in/var/cachewith the appropriate permissions. Your use case sounds like something advanced which is out of scope for the Django documentation.