On Sun, Jun 10, 2012 at 10:38 AM, Anthony <abasta...@gmail.com> wrote:
> 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...
>> Both of those options are a lot more involved and disruptive than just
>> changing a symbolic link.
> 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).
So, I have to get to the headless production server (ssh in).
Start a localport only duplicate web2py server.
Setup an SSH tunnel so I can get to the locaport only server.
then I can finally point my browser at it and click to get the admin
and click to get the routes reloaded.
OR
I can just ssh to the server.
then move a symlink.
Moving a symlink is a lot easier. If it is trustworthy.
>> 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.
"It works for me the few times I tried it" isn't an answer I'm going
to trust for a running production server. I've been doing software for
far too long to fall for that! :-)
Thanks,
-Doug
