Ghost folder & file permissions
See original GitHub issueIn an ideal world, we’d set the folder permissions to be 774 and the file permissions to be 664 for everything inside a ghost directory:
e.g.
find /path -type d -exec chmod 774 {} \;
find /path -type f -exec chmod 664 {} \;
For now they have been set to 774 as a shortcut to a good, if not the best, solution.
This would need to be done on initial install, and probably rechecked/rerun on version folders after an install.
Issue Analytics
- State:
- Created 6 years ago
- Comments:8 (8 by maintainers)
Top Results From Across the Web
Problems with permission, I need help, I am 2 days trying to ...
Checking if logged in user is directory owner > Message: Your user does not own the directory /var/www/ghost and is also not a...
Read more >If I try to delete the Ghost folder I get the message "Could not
If I use cmd with admin permissions to bring up the directory, the file is listed as being there but using "rmdir" to...
Read more >I need to remove ghost inherited permission from a folder on ...
I have a folder something like this E:\Folder1\Folder2 Folder2 shows that there is a permission of AD object which no longer exists (which ......
Read more >Setting permissions - Ghost Solution Suite - TechDocs
Set permissions for jobs, job folders, computers, and computer groups. ... These permissions include access to remote operations using Ghost Solution Suite ...
Read more >Folder with ghost permissions - cannot delete!
Create a folder with inheritance enabled and move the ghost folder into it to try and force inheritance. Tried various file / folder...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Update, after reading through https://www.cyberciti.biz/tips/understanding-linux-unix-umask-value-usage.html the correct permission for directories is
775
. Using775
on files would make all files executable for every user which is unwanted.Correct commands:
After some testing with the new permission checks, it turned out that Ghost itself creates files with a
644
permission (e. g. log files). We decided to change the checks and allow644
and665
for files, and775
and755
for directories. The recommendation to the user is - in both cases - to change it to the stricter one.