Re: [web2py] Re: nginx + uwsgi + web2py + PAM

2013-04-03 Thread Matt Broadstone
Man, we're still using web2py 2.0.9 so that was definitely not in the script before! That would have saved me a day of work :) Matt On Tue, Apr 2, 2013 at 3:41 AM, Niphlod wrote: > nice. The script shipped with web2py installs uwsgi from pip, so we're > covered! > > On Monday, April 1, 2013 4:48

Re: [web2py] Re: nginx + uwsgi + web2py + PAM

2013-04-02 Thread Niphlod
nice. The script shipped with web2py installs uwsgi from pip, so we're covered! On Monday, April 1, 2013 4:48:59 PM UTC+2, Matt wrote: > > On Fri, Mar 29, 2013 at 12:15 PM, Matt Broadstone > > > wrote: > > On Fri, Mar 29, 2013 at 12:05 PM, Niphlod > > wrote: > >> uhm. Before smashing heads a

Re: [web2py] Re: nginx + uwsgi + web2py + PAM

2013-04-01 Thread Matt Broadstone
On Fri, Mar 29, 2013 at 12:15 PM, Matt Broadstone wrote: > On Fri, Mar 29, 2013 at 12:05 PM, Niphlod wrote: >> uhm. Before smashing heads against the wall, there are 3 different >> "available methods" here. >> >> 1) rely on nginx to authenticate users through pam (kinda of a basic auth, >> bu

Re: [web2py] Re: nginx + uwsgi + web2py + PAM

2013-03-29 Thread Matt Broadstone
On Fri, Mar 29, 2013 at 12:05 PM, Niphlod wrote: > uhm. Before smashing heads against the wall, there are 3 different > "available methods" here. > > 1) rely on nginx to authenticate users through pam (kinda of a basic auth, > but checked against PAM) > 2) rely on uwsgi to authenticate users t

[web2py] Re: nginx + uwsgi + web2py + PAM

2013-03-29 Thread Niphlod
uhm. Before smashing heads against the wall, there are 3 different "available methods" here. 1) rely on nginx to authenticate users through pam (kinda of a basic auth, but checked against PAM) 2) rely on uwsgi to authenticate users through pam (kinda of a basic auth, but checked against PAM

[web2py] Re: nginx + uwsgi + web2py + PAM

2013-03-29 Thread Matt Broadstone
For further info, these are relevant configuration files: /etc/nginx/sites-enabled/site: server { listen 80; server_name $hostname; rewrite ^ https://$server_name$request_uri? permanent; } server { listen 443; server_name $