in a shared host, there must always be someway to restart your applicacation. If hosting is using mod_wsgi (for example), you can restart your application hosted by mod_wsgi by restarting mod_wsgi (see http://code.google.com/p/modwsgi/wiki/ReloadingSourceCode <http://code.google.com/p/modwsgi/wiki/ReloadingSourceCode>- we setup so you "touch" the script file; this is enough to cause a reload)
Also, different providers offer different restart mechanisms for your application. Check with support. For example, on webfaction you have your own instance of apache, so you simply can do something as simple as: $ ~/webapps/myapp/apache2/bin/restart On Mon, Apr 13, 2009 at 8:05 AM, Álvaro Justen [Turicas] < [email protected]> wrote: > > On Mon, Apr 13, 2009 at 2:34 AM, mdipierro <[email protected]> > wrote: > > This is not an easy one. The problem is that the routes code is > > outside any app. Currently if there is a bug in routes, web2py does > > not start. If you allow changes at runtime: 1) you make web2py slower > > because changes have to be monitored; 2) what happens if there is a > > bug in routes? > > Yes, I know about that problems. But in a shared host, what I can do > to solve this? > > -- > Álvaro Justen > Peta5 - Telecomunicações e Software Livre > 21 3021-6001 / 9898-0141 > http://www.peta5.com.br/ > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. 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/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
