Robert, I've updated my server to use the latest nginx PPA and did a pip install of uwsgi 'latest' (v0.9.7). Here is my configuration, using emperor mode:
/usr/bin/uwsgi --emperor /etc/uwsgi/sites -d /var/log/uwsgi.log I have a skeleton vassal /etc/uwsgi/app.skel which I symlink into the /etc/uwsgi/sites directory with the appropriate name. This is my app.skel file contents: [uwsgi] uid = %n gid = %n socket = /tmp/%n.sock chmod = 666 chdir = /home/%n home = /home/%n logto = /home/%n/logs/uwsgi.log module = wsgiapplication master = true processes = 4 vacuum = true So, if I have '/etc/uwsgi/sites/example.ini', that means I have a 'example' user and group. In the 'example' user's home directory (/home/example) is where I have my Django application - each user runs a single Django application. With the uid/gid parameters in the INI file, if files are generated or uploaded, they are stored with the correct user/group ownership set. The problem I'm seeing is that the log file created at /home/example/logs/uwsgi.log is owned by root most of the time. I have seen them owned by the 'example' user occasionally, but I don't know why. I would presume that since the vassal uwsgi process group is running as the 'example' user, the log file would be written out with 'example' user/group ownership. I would appreciate your insight. If you have any other tips for my configuration, please feel free to share! Thanks, James
_______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
