You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
find "$install_dir" -type f -exec chmod 640 {} \;
find "$install_dir/bin" -type f -exec chmod 750 {} \;
find "$install_dir" -type d -exec chmod 750 {} \;
find "$install_dir" -type d -exec chmod +s {} \;
It all works like a charm until one starts using grav admin. The admin saves in the following way:
-rw-r--r-- someNewFile
drwxr-sr-x someNewDir
So if I translate it right it means 644 for files and 755 for directories.
It's not creating issues with site functionalities, but it would be cleaner if one could instruct the admin to set permissions like done on install. I didn't find a way to do that though, but don't know grav admin so well and there might be a functionality to do so.
Anyway just wanted to post about it for the record and in case someone has some reflections on this, but as said in the beginning, if it's not really fixable, the issue can be closed.
Context
I have access to my server: Through SSH, through the webadmin
Are you in a special context or did you perform some particular tweaking on your YunoHost instance?: no
YunoHost version: 11.2.10.3
Grav_ynh version: 1.7.44~ynh1
The text was updated successfully, but these errors were encountered:
Describe the bug
This is a minor issue, so feel free to close it.
By default grav seems to recommend using the following way to set permissions:
Grav_ynh's approach is to be more restrictive, which works and looks nice to me:
It all works like a charm until one starts using grav admin. The admin saves in the following way:
So if I translate it right it means 644 for files and 755 for directories.
It's not creating issues with site functionalities, but it would be cleaner if one could instruct the admin to set permissions like done on install. I didn't find a way to do that though, but don't know grav admin so well and there might be a functionality to do so.
Anyway just wanted to post about it for the record and in case someone has some reflections on this, but as said in the beginning, if it's not really fixable, the issue can be closed.
Context
The text was updated successfully, but these errors were encountered: