"Why would anybody want to use sockets when they can cause permission problems? TCP is so much more straight forward."
I only use unix sockets with uWSGI and it is very straightforward, never had any problems. It is very convenient to use named sockets instead of juggling numbers if you are using multiple uwsgi process for multiple sites on the same server.
You shouldn't even have to use CHOWN on or create the unix socket file yourself. Just specify the socket name and add "-C" or "666" to your uWSGI config.
Comment
Thanks for the tip!
Parent comment
"Why would anybody want to use sockets when they can cause permission problems? TCP is so much more straight forward." I only use unix sockets with uWSGI and it is very straightforward, never had any problems. It is very convenient to use named sockets instead of juggling numbers if you are using multiple uwsgi process for multiple sites on the same server. You shouldn't even have to use CHOWN on or create the unix socket file yourself. Just specify the socket name and add "-C" or "666 " to your uWSGI config.