Hi Carlos, Thanks for replying. I have added following two options in [uwsgi] section of production.ini that I have posted. plugin = python paste = config:/home/web/projects/example22/production.ini
I think that it takes care of the alternate options on command line Besides when I use a tcp socket instead of file socket and run http server using uwsgi directly, I am able to see it on browser using uwsgi. But for some strange reasons, I can't get nginx to display uwsgi thing. PS: uwsgi in python does not have --ini-paste and --paste options for some strange reasons. On Tuesday, 26 June 2012 01:19:02 UTC+5:30, Carlos Daniel Ruvalcaba Valenzuela wrote: > > On Mon, Jun 25, 2012 at 8:04 AM, alind > <[email protected]<[email protected]>> > wrote: > > Reading a bit more on internet, I understood (dont know if correctly) > that > > wsgi section should be put in productiion.ini of my TG product. > > Here is the productio.ini file -> http://pastebin.com/GfVijDUc > > Running uwsgi inside by virtualenv with command runs. > > uwsgi --ini production.ini > > The --ini option is to specify an ini file with the uwsgi config, what you > are looking for is the --paste option which specifies the absolute path to > your production.ini (or development) file, just add the paste option on you > uwsgi ini config. > > Regards, > Carlos Daniel Ruvalcaba > -- You received this message because you are subscribed to the Google Groups "TurboGears" group. To view this discussion on the web visit https://groups.google.com/d/msg/turbogears/-/OWpSju2tArsJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/turbogears?hl=en.
