Linux – Uwsgi – Socket file or URL

debianlinuxsocketuwsgi

I was installing UWSGI and it looks like for the socket I can specify either a URL and port or instead I can specify a socket location file.

I was wondering if anyone can tell me what the difference is between these two, and if one is preferable to the other.

Thank you.

Best Answer

You can run uwsgi to listen to a TCP/IP port, for example uwsgi --http :80 , if you change it to listen to a Unix socket (for ex: uwsgi --socket :8000 ) then this is local only, no web service (TCP/IP) is exposed to the Internet and you have to put a web server like nginx in front of uwsgi as 'proxy' that can get the http requests from the outside world (see https://gist.github.com/evildmp/3094281 for a django example instead of Flask)

Related Solutions

Ssh – Forward local port or socket file to remote socket file

Altough in the time, when the question was asked, it was really impossible, but it is possible nowadays.

You can to both: UNIX=>TCP and UNIX=>UNIX forwarding.

For example:

ssh \
  -R/var/run/mysql.sock:/var/run/mysql.sock \
  -R127.0.0.1:3306:/var/run/mysql.sock \
  somehost

It is possible since OpenSSH 6.7.

Hostname Appears as 127.0.1.1 Instead of 127.0.0.1 in /etc/hosts

There isn't a great deal of difference between the two; 127/8 (eg: 127.0.0.0 => 127.255.255.255) are all bound to the loopback interface.

The reason why is documented in the Debian manual in Ch. 5 Network Setup - 5.1.1. The hostname resolution.

Ultimately, it is a bug workaround; the original report is 316099.

Best Answer

Related Solutions

Ssh – Forward local port or socket file to remote socket file

Hostname Appears as 127.0.1.1 Instead of 127.0.0.1 in /etc/hosts

Related Topic