Gunicorn.sock files : How are they generated? Where should they be located?

February 26, 2015 3k views

Hi I'm currently trying to follow a tutorial on installing nginx with gunicorn and django. I've combed the web for more docs/explanation on the gunicorn.sock file, it's contents and location.

So far all the tutorials I've seen include such a file, but do not explain fully their purpose. Can anyone on digital ocean shed more light on these? I've done a search for 'gunicorn.sock' on but I get the boilerplate 'Your search did not match any documents...'

Thanks in advance :-)

3 Answers

Hi, Sock files are Unix domain sockets that processes use to communicate - in this case, Gunicorn uses its .sock files to talks to other parts of the process.

yeah i've had the same questions for awhile now as well. Several tutorials on deploying django, gunicorn and nginx talk about daemonizing/automating gunicorn but in the conf files, it specifies a .sock file. where is this .sock file? is it usually created automatically by whichever WSGI you choose i.e uWSGI, gunicorn? i tried to find the .sock file for my respective django app on ubuntu using find command but no luck. i want to use supervisor to automate gunicorn but i dont fully understand the conf file for superviser.

you can specify the sock file you want to create with --bind flag in gunicorn --bind unix:/home/youusername/somename.sock.

In nginx you can do.

location /home/ {
        proxy_pass http://unix:/home/youusername/somename.sock;
Have another answer? Share your knowledge.