-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/10/2014 12:13 AM, Roberto De Ioris wrote:
> This covers basically any aspect of a production
> ready-deployments:
>
> http://uwsgi-docs.readthedocs.org/en/latest/WSGIquickstart.html
>
> as you can see it uses tcp sockets when describing nginx
On Thursday 09 October 2014 10:49:38 Greg Barker wrote:
> Option #2 should work, here's what I have for my uwsgi site. Double check
> your permissions on the directory the uwsgi.sock lives in.
>
> My nginx conf:
> location / {
> uwsgi_pass unix:///var/www/my_app/my_virtualenv/run/uwsgi.sock;
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 10/09/2014 12:49 PM, Greg Barker wrote:
>> Option #2 should work, here's what I have for my uwsgi site.
>> Double check your permissions on the directory the uwsgi.sock lives
>> in.
>>
>> My nginx conf: location / { uwsgi_pass
>> unix:///var
Shouldn't matter that you don't have a www-data user, that just happens to
be the one I am using. I am running uwsgi in emperor mode so my worker
processes have that uid
$ ps aux | grep uwsgi
root 798 0.0 0.0 31748 2296 ?Ss Sep29 0:24
/var/www/my_app/my_virtualenv/bin/uwsgi -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/09/2014 12:49 PM, Greg Barker wrote:
> Option #2 should work, here's what I have for my uwsgi site.
> Double check your permissions on the directory the uwsgi.sock lives
> in.
>
> My nginx conf: location / { uwsgi_pass
> unix:///var/www/my_app/m
Option #2 should work, here's what I have for my uwsgi site. Double check
your permissions on the directory the uwsgi.sock lives in.
My nginx conf:
location / {
uwsgi_pass unix:///var/www/my_app/my_virtualenv/run/uwsgi.sock;
include uwsgi_params;
}
Directory permissions:
$ ls -la /var/ww
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have been trying to get nginx to talk to uwsgi to no avail. uwsgi
works by itself as I can host it on port 80 on my local machine with no
problems. I have tried configuring nginx with the following variations:
# option 1
location / {
include uws
