Hi All

I've recently started working for a dedicated hosting company, and I'm trying to get a better understanding of the permissions surrounding Apache, particularly when different PHP handlers are used. For example, a common issue encountered by customers is permissions relating to Wordpress installs, whereby sites frequently need to be set to use FastCGI rater than mod_php, or need custom write permissions or ACLs set on directories for various users to enable uploads. There also seems to be differences in the Apache user between Red-Hat based system, and Debian based systems (in terms of naming standards, anyway.

I'm attempting to piece together my own overview from various sources on the net, but having spent some time googling and reading up, I'm still a bit confused as to the exact interplay between basic Apache permissions, CGI, FastCGI, suPHP and suEXEC, and how they apply to CMS systems like Wordpress and Joomla etc...

We also use a couple of different control panels, primarily Plesk (but also cPanel), so certainly in the case of Plesk there are default ftp user groups such as psacln which might need to be taken into further account.

I'm not going to ask anybody to spell it all out for me, but as of yet I've not been successful in tracking down a reasonable overview on the subject online, I'm trying to combine information from various sources, not all of which is necessarily up-to-date.

Would anybody out there happen to have some links to any decent resources or tutorials on Apache permissions/PHP handlers that would help me wrap my head around it a bit better?

Any help much appreciated.

Cheers.


Alex.

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
  "   from the digest: users-digest-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org

Reply via email to