We are transitioning over to a new forum platform. Please post new issues there. Existing threads will be dealt with here unless you choose to move them over. Visit the new forum
Explicit Perch Directory Access Permissions
Hi there, I'm looking for a canonical list of all the directories that Perch writes and needs to execute. As it stands, there is only one place that I could find that lists the folders which require write access and it was https://docs.grabaperch.com/perch/getting-started/installing/ in the section where it mentions 'Final Steps' and even here it only mentions 'perch/resources'.
I need this information as our client uses SELinux which requires mandatory access control to be set up with every application, and we must explicitly state which folders Perch will write to, so until we know exactly what folders Perch may write to, we cannot guarantee that the application will not flip out when something is modified.
The directories that I have come up with so far that seem to require write access are as follows: perch/resources perch/addons/apps/perch_blog/lang/ perch/core/lang/
I believe there is logic to do with how the templates work, in terms of them getting copied to new locations and thing, but I am not sure on this, and there may be something to do with the backups that Perch makes as well.
This is incredibly important as this can make or break whether we use Perch.
In general, when a company creates a piece of software they should list all folders that require write access, not 1 out of many, this seems a bit naive.
If Perch aren't willing to do this themselves, I urge anyone with more information to contribute to this post so we can come up with a canonical list for other users to use who may be experiencing issues with setting up Perch on SELinux hardened Linux machines.
Want to reply to this thread?Login with Perch