#21219: The FILE_UPLOAD_PERMISSIONS should not be used when deploying static
files
-------------------------------------+------------------------------------
Reporter: dblack+django@… | Owner: vajrasky
Type: New feature | Status: closed
Component: contrib.staticfiles | Version: master
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+------------------------------------
Changes (by Tim Graham <timograham@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"9eecb9169566db263e243e4522b08ea1403ee95f"]:
{{{
#!CommitTicketReference repository=""
revision="9eecb9169566db263e243e4522b08ea1403ee95f"
Fixed #21219 -- Added a way to set different permission for static files.
Previously, when collecting static files, the files would receive
permission
from FILE_UPLOAD_PERMISSIONS. Now, there's an option to give different
permission from uploaded files permission by subclassing any of the static
files storage classes and setting the file_permissions_mode parameter.
Thanks dblack at atlassian.com for the suggestion.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/21219#comment:11>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/085.6318e0b6f2fbca342dfaa69db0be27c3%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
