When in development config when running on my Windows laptop (using localhost in browswer), I enjoyed the convenience of TG dynamically accounting for each save of an edit to 'controllers.py'.
But now I've moved my code over to a Solaris Unix system on which I'm running in production config (using the Unix computer's URL in browser), and in this situation it seems that to have each edit to 'controllers.py' take effect, I must Control-C to interrupt my "python start-hello.py" and then restart it again. I'm using the same version of TG on each system (latest version as of last week), and both systems are using Python 2.4. The good news is that the edits do take effect after I do this, but the bad news is it's less efficient to make changes. I don't know which factor (dev config using localhost vs. prod config using real URL, or Windows vs. Solaris/Unix) is making this difference. On the production system, I'm using the simple web server that's built- in to TG (not Apache). A possibly related question: is there a way I can easily leave the TG server running after I log out of my session on the server? I recall from past work that Tomcat/Java allows that, so I'm hoping TG does as well. (For example, perhaps there's some optional way to start it instead of running "python start-hello.pc" from the command line, which obviously interrupts when I close the remote Unix terminal to shut off my laptop). --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
