I hope that this has not already been covered elsewhere in the forum. (I did several searches, I swear!)
I am trying to design a configuration for the WP server for my College, where several people will share the same server, but should be limited to their own installation of WP. This is largely for security reasons (so that a rogue plugin or sloppy coding on one site can't affect every other WP install on the same server).
I've found (slightly contrary to the codex I think-I intend to see about editing that: separate subject) that the user which runs PHP (Apache usually as 'nobody' or similar) has to OWN the files/directories, not just be allowed to write there. This leads me to suexec or suPHP. I found in another thread that suexec and suPHP are definitely different. The still lingering question is whether I should be using suPHP (last updated in 2009!) or whether suexec will get the job done.
PHP in wp1/ will run with person X's owner's permissions, allowing automatic updates, plugins which create/change files, etc.
PHP in wp2/ will run with person Y's owner's permissions, allowing all functionality, but keeping them out of wp1/ (and vice versa).
(I intend for wp1/ and wp2/ to be multisite networks BTW. Not a dealbreaker if this won't work, but it would be nice.)
After struggling (and failing) to get Apache configured and running properly with suPHP, I'm wondering if I'm chasing the wrong target and I should just be using suexec somehow?