I Think I tracked down the issue.
In the windows service, it just imports the HttpServer class from main, and
then creates one using the options.py for its settings.
However, when starting a web2py not as a service, it makes a call to main.py
In gluon.main.py we can see that rewrite.load is imported and then later
just run with global file scope as a call to load()
This however is not done in association to creating or starting a
web-server so when the windows service creates the HttpServer object no
call is made to load()
To fix this edit gluon.winservice.py, and add the following lines to the
try block in the start function
...
try:
from rewrite import load
load()
self.server.start()
except:
....
This causes it to read the routes.py file before starting the server and
should cause the desired action.
On Monday, August 20, 2012 12:15:25 AM UTC-4, Dave wrote:
>
> I generally am not the person to be monkeying around with things on
> Windows. That said, one of my customers is about to take over management
> and ownership of a web2py application I have written for them. I seem to
> be having an issue testing the deployment for them.
>
> I created an options.py file and the service installs and starts properly.
> Unfortunately, for some reason it does not appear the routes.py file is
> being parsed on startup though. Even though the default app is set, a
> request to / still attempts to go to /welcome/... If I go in to the admin
> interface and choose reload routes, everything works... until the service
> is restarted that is.
>
> If I run web2py from the command line .. ie python web2py.py -p 80 -a
> 'password', the routes.py file gets parsed on startup.
>
> Any ideas?
>
--
---
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to web2py+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
