I've tried touching and renaming the fcgi file but I can't see any changes. Either it hasn't picked up the changes, or I've done it wrong. Any way of knowing if routes.py has kicked in ? P.S. I'm running shared on HostGator, with no admin (ssl) access. Will killing all the fcgi running processes help ?
On Sunday, October 24, 2010 2:48:42 AM UTC+13, cjrh wrote: > On Oct 22, 11:49 pm, Jonathan Lundell <jlund...@pobox.com> wrote: > > Just a reminder: a change to routes.py won't be noticed until you > restart web2py (or explicitly do a reload). > > Yes, I touch the web2py.fcgi file so that Apache restarts the > process. So I assume that the web2py process was restarted. I'd > need to add logging and such to make sure tho. --
