I use `screen` and keep my web.py app long-running on a secondary screen during development. I can toggle to it to catch debug and/or restart when `web.reloader` might not be sufficient. I don't lose any screens upon killing my local terminal. After a local reboot or a drop in the connection I can simply `screen -r` to resume my session. I can point you down the right path if this will help your particular situation.
Otherwise, are you talking about daemonizing your app? For stability and performance you likely *don't* want to do this but if your situation calls for it — http://www.jejik.com/articles/2007/02/a_simple_unix_linux_daemon_in_python/ Let me know if that helps. On Sat, Nov 7, 2009 at 6:41 AM, geekbuntu <[email protected]> wrote: > > right now i have a terminal window running my webpy app - is there a > way to make it run by itself - not dependent on it being executed > manually? (like a standard webserver) > > > > -- Angelo Gladding [email protected] http://angelo.gladding.name/ E69E 47E8 5C3A 96E5 C70F D931 F35C ACBA 6F39 9611 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web.py" 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/webpy?hl=en -~----------~----~----~----~------~----~------~--~---
