Last active
April 8, 2020 15:46
-
-
Save patomarques/ad6b3d2fdfbeb463914c0c61e156ce9d to your computer and use it in GitHub Desktop.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| ## wordpress permissions | |
| ## When you setup WP you (the webserver) may need write access to the files. So the access rights may need to be loose. | |
| chown www-data:www-data -R * # Let Apache be owner | |
| find . -type d -exec chmod 755 {} \; # Change directory permissions rwxr-xr-x | |
| find . -type f -exec chmod 644 {} \; # Change file permissions rw-r--r-- | |
| After the setup you should tighten the access rights, according to Hardening WordPress all files except for wp-content should be writable by your user account only. wp-content must be writable by www-data too. | |
| chown <username>:<username> -R * # Let your useraccount be owner | |
| chown www-data:www-data wp-content # Let apache be owner of wp-content | |
| Maybe you want to change the contents in wp-content later on. In this case you could | |
| temporarily change to the user to www-data with su, | |
| give wp-content group write access 775 and join the group www-data or | |
| give your user the access rights to the folder using ACLs. | |
| Whatever you do, make sure the files have rw permissions for www-data. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment