Skip to main content
Unix & Linux

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

7
  • Thank you slm, this is very helpful. I will try it out and let you know. Couple of questions: apache apache - Does that refer to the user apache and group apache? If I assign apache as the owner, what command do I need to issue so that apache alone is the owner and not bluegig eg. chmod 775 wp-content ? Also, What command do I use to make the apache user the owner - chown apache wp-content? Commented Jul 9, 2013 at 11:31
  • chmod -R apache.apache wordpress will change the user/group to apache for the entire directory wordpress. Permissions should be 775, so that only the user apache and group apache can access the directory. Commented Jul 9, 2013 at 11:33
  • thanks slm. You say only apache group and user will be able to access the folder - do you mean write access?...But certainly public must be able to view the files, how else will they see the website over port 80 on a web browser? Commented Jul 9, 2013 at 12:07
  • @DextrousDave - the file permissions don't really have anything to do with someone accessing a page through the webserver. Remember that the webserver is a process that opens the files, reading them in and then serves them to browsers as they connect to the server. The permissions are only in play when someone is directly logging into the server as a given user on the system. Commented Jul 9, 2013 at 13:34
  • of course, that makes sense. Just had a blonde moment.Thank you very much. I managed to make apache the owner and I added him to the bluegig group. Now I have write access inside wordpress. Commented Jul 9, 2013 at 14:39