#16886 closed Bug (fixed)
Memcached socket file usage is undocumented
| Reported by: | Daniel D. Beck | Owned by: | nobody |
|---|---|---|---|
| Component: | Documentation | Version: | dev |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Ready for checkin | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
The Memcached docs do not describe how to use CACHES with Memcached and a Unix socket file. The most Google-able instructions, found in ticket #10168, do not apply the Django 1.3+ method of configuring caches.
Such docs would be particularly useful to users in shared hosting environments, since Memcached does not provide any kind of authentication. With socket file permissions, such users can protect their instance of memcached from unauthorized use.
Attached, you'll find my proposed addition to the docs to make this usage more discoverable.
Attachments (1)
Change History (6)
comment:1 by , 13 years ago
| Triage Stage: | Unreviewed → Accepted |
|---|
by , 13 years ago
| Attachment: | memcached_socket_doc.diff added |
|---|
comment:2 by , 13 years ago
Thank you for the feedback. I tested it without the double unix: and it works appropriately. I updated the patch to remove the double unix: and to add the missing comma.
comment:3 by , 13 years ago
| Triage Stage: | Accepted → Ready for checkin |
|---|
Looks great! Thanks for checking that out, and thanks for the contribution!
Is the double unix: really required for this to work? I know it wasn't with the CACHE_BACKEND setting.
Otherwise (with an added comma to clarify that the unix-path section is separate from the ip:port section) this looks good to me.