Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!eternal-september.org!feeder.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail From: Veek M Newsgroups: comp.lang.python Subject: Re: uWSGI, nGinx, and python on Wheezy: how do you configure it? Followup-To: comp.lang.python Date: Wed, 17 Dec 2014 08:01:43 +0630 Organization: Home Lines: 15 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8Bit Injection-Date: Wed, 17 Dec 2014 02:31:20 +0000 (UTC) Injection-Info: mx02.eternal-september.org; posting-host="18c6de602bac5de34a7414225a720dd2"; logging-data="18356"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/ipjgmJ8j/FIUwuW+v61i/" User-Agent: KNode/4.4.11 Cancel-Lock: sha1:7pb7It0y30QLzkuXHDTIoZr0Qg4= Xref: csiph.com comp.lang.python:82589 Chris Warrick wrote: > This is NOT how uwsgi works! You cannot use plain .py files with it, > and for good reason ? CGI should be long dead. > > What you need to do is, you must write a webapp ? in Flask, for > example. Then you must craft an .ini file that mentions this. **Hi Chris, Could you suggest some specific document (URL) that illustrates the working principle behind uWSGI?** I only know CGI so.. i'm beginning to think uWSGI works with single python files as in, with CGI, the user can pretty much pick any .py: foo.py, bar.py, imaginary.py merely by editing his URL request. With uWSGI you generally start one .py file and use that to access the larger framework/library?