Opened on 10/09/2015 at 07:24:51 PM
Closed on 10/13/2015 at 11:12:44 AM
Last modified on 10/13/2015 at 11:34:44 AM
#3190 closed defect (fixed)
Fix CMS cache path permissions
Reported by: | matze | Assignee: | matze |
---|---|---|---|
Priority: | P2 | Milestone: | |
Module: | Infrastructure | Keywords: | |
Cc: | fred | Blocked By: | |
Blocking: | Platform: | Unknown / Cross platform | |
Ready: | yes | Confidential: | no |
Tester: | Unknown | Verified working: | no |
Review URL(s): |
Description
The CMS we are using for static content attempts to create a directory for intermediate files, e.g. /var/cache/$repository. Since the associated scripts are not executed as user root, which is the only one allowed to change the fist-level content of /var/cache, this operation fails due to insufficient permissions.
Workaround
Create the respective sub-directory in manual fashion upfront.
Todo
- Extend class web::server to include the creation of /var/cache/$repository
- Ensure the cache directory is owned or just writable by user www
- Suggest the use of a distinct sub-directory, e.g. /var/cache/cms, or providing a configuration option, at least
Attachments (0)
Change History (2)
Note: See
TracTickets for help on using
tickets.
https://hg.adblockplus.org/infrastructure/rev/bc42b98931a9