On Wed, 2014-03-26 at 05:13 -0700, Linda Walsh wrote:
lynn wrote:
13.1 Hi We have a nginx test going. Yast created a uid:gid, nginx:nginx Is that if you are running apache at the same time?
If we go live, is there any reason nginx shouldn't run as: wwwrun:www
No prob, unless you do the same with another piece of SW.
Several packages have tended to overlap on UID or GID and it, generally speaking, is more secure to put each in their own group. That way you could, say, give out access to nginx to someone, w/o them having access to the output of ntop (which also was switched to it's own user/group away from overlapping on wwwrun:www.
From what I understand, wwwrun:www is to be use for a web server.
But you can reuse it if you know you'll never need the standard functions...
Hi Thanks, that sounds good. We've an app where the devs want to rw stuff to their public_html folder. Apache writes as wwwrun:www whereas the 13.1 nginx writes as nginx:nginx: they can't edit their files any longer. Rather than go through all the public_html folders on the fs, I'd rather just change nginx.conf to wwwrun:www. We've tried it and it works but I doubt it's as simple as that. I've usually overlooked something. L x -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org