#32176 closed Cleanup/optimization (fixed)
Outdated LOCATION requirement in Filesystem caching docs.
| Reported by: | Carles Pina Estany | Owned by: | Carles Pina Estany |
|---|---|---|---|
| Component: | Documentation | Version: | dev |
| Severity: | Normal | Keywords: | |
| Cc: | Carles Pina Estany | Triage Stage: | Ready for checkin |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | yes | UI/UX: | no |
Description (last modified by )
In: https://docs.djangoproject.com/en/3.1/topics/cache/#filesystem-caching
It says that LOCATION needs to exist. But the code creates it if it doesn't exist:
https://github.com/django/django/blob/354c1524b38c9b9f052c1d78dcbfa6ed5559aeb3/django/core/cache/backends/filebased.py#L116 called from https://github.com/django/django/blob/master/django/core/cache/backends/filebased.py#L23
Current documentation:
Make sure the directory pointed-to by this setting exists and is readable and writable by the system user under which your Web server runs. Continuing the above example, if your server runs as the user apache, make sure the directory /var/tmp/django_cache exists and is readable and writable by the user apache.
Change History (7)
comment:1 by , 4 years ago
comment:2 by , 4 years ago
| Cc: | added |
|---|
comment:3 by , 4 years ago
| Description: | modified (diff) |
|---|
comment:4 by , 4 years ago
| Summary: | Filesystem caching documentation incorrect → Outdated LOCATION requirement in Filesystem caching docs. |
|---|---|
| Triage Stage: | Unreviewed → Accepted |
| Type: | Bug → Cleanup/optimization |
comment:5 by , 4 years ago
| Triage Stage: | Accepted → Ready for checkin |
|---|
Note:
See TracTickets
for help on using tickets.
See PR: https://github.com/django/django/pull/13649