> > > Reloading routes does not restart the server -- it just re-reads the > routes > > file. > > OK... just checked the code for the stable release... but, unless the > docs say so, I can't really rely on that behaviour not changing... >
Aside from the built-in Rocket server (which is primarily intended for development), web2py doesn't have any control over the server so can't generally restart your server -- so you should be able to rely on the fact that reloading routes will not be achieved by restarting the server. > > I don't think clicking a button is any more involved or disruptive than > > changing a symbolic link, but you can make it even easier by simply > visiting > > the /admin/default/reload_routes URL (if you're not logged in to admin > at > > the time, you'll be prompted to login before routes.py is reloaded). > > Actually, that is assuming a debug/development server. > The docs say not to leave that enabled for a production server (I > followed that advice). > No, admin (including reloading routes) can be made available on a production server -- you just have to access it via HTTPS. This should be fine for production. >> BUT would changing a symbolic link on a running server cause problems? > >> Where do I find that out? > > > > > > Probably won't be a problem. Best way to find out is to try it. > > Well... that's not a good enough answer to trust for production. Sure > I can test it on a dev server, but all that really means is that it > didn't cause a problem the few times I tried it. > What's the potential problem? Changing the symlink either points to the new app or it doesn't -- if it does, you should be good to go. Anthony
