On 10 Dec 2012, at 4:33 AM, Vinicius Assef <[email protected]> wrote: > > Actually, I needed to restart uwsgi, not nginx.
The reload routes button is insufficient when you're running in a multiprocess (vs single-process multithreaded) environment, because only one process sees the button press. > > > > On Mon, Dec 10, 2012 at 10:29 AM, Vinicius Assef <[email protected]> > wrote: >> I created a routes.py script in web2py root with only this line: >> default_application = 'myapp' >> >> Then, I clicked "reload routes" button in the admin app, but no effect >> take place. >> >> Things just worked out when I restarted nginx via command line. >> >> It it supposed to work this way? Should I really restart nginx to >> routes.py take effect? --
