Friday, November 28, 2014

Ideal permissions scheme for multiple Apache/PHP sites

I'm hosting multiple sites from one server where each site has it's own user and www directory in their home dir. Currently our web server runs as user nobody(99). We're noticing that to run several popular scripts and engines, they require write access to their own files.



As the home directory is owned by the user, not nobody(99), what is the best policy or change in hosting configuration that would:




  • ...make it so that all the various engines and platforms work?

  • ...still allow us to work with files and edit them without having to diddle with permissions as root?

  • Doesn't require me to massage permissions and/or ownership with every file change.




Thanks for the advice!

No comments:

Post a Comment

linux - How to SSH to ec2 instance in VPC private subnet via NAT server

I have created a VPC in aws with a public subnet and a private subnet. The private subnet does not have direct access to external network. S...