On Fri, Mar 18, 2011 at 1:13 PM, Roberto De Ioris <[email protected]> wrote:
>
> > nginx.conf snippet:
> >
> > location ~ \.py$ {
> > uwsgi_pass 127.0.0.1:3031;
> > include uwsgi_params;
> > uwsgi_param UWSGI_PYHOME /u1/www/corbe.net;
> > uwsgi_param UWSGI_CHDIR /u1/www/corbe.net;
> > }
> >
> >
>
> If i understand correctly you are forcing users to a php-like approach
> writing a WSGI app for every url.
>
> Is this your idea ?
>
>
Yes but there's a little more to it than that. Some of my users are
starting to "I want python" without really knowing why or how to deploy
python applications and I want to be as uninvolved in the development aspect
of their sites as possible.
So the answer to your question is yes: I want to provide a "PHP way of
doing things for Python users" without having to use FastCGI and flup mostly
because the flup author himself has renounced FastCGI.
> Honestly i do not think that users will love this solution as none of the
> WSGI framework/apps out there works in this way.
>
I agree with you here. For experienced users who actually do want wsgi I'm
willing to do custom configurations for them and assist them in setting
their applications up. For inexperienced users that just want to hack on
python the hands-off PHP method is better.
>
> By the way, if you want to follow this path you can use uWSGI for sure and
> i will send you a configuration template.
>
This would be awesome of you. Thanks.
> --
> Roberto De Ioris
> http://unbit.it
> _______________________________________________
> uWSGI mailing list
> [email protected]
> http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
>
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
