Opened 4 years ago

Closed 4 years ago

Last modified 4 years ago

#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):

https://codereview.adblockplus.org/29329028/

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

Change History (2)

comment:1 Changed 4 years ago by matze

  • Resolution set to fixed
  • Review URL(s) modified (diff)
  • Status changed from new to closed

comment:2 Changed 4 years ago by matze

Follow-up suggested in #3198.

Note: See TracTickets for help on using tickets.