buffalob wrote: > Dom, thanks much for reply. The reason for having TG running in prod > config even while still doing some "developing" on the unix server is > that some of the use cases I'm working on involve some two-way > interaction with with external web apps on other computers (and my > understanding is that TG running in dev config does not allow access > via a real URL - only standalone "localhost", correct?) Wrong :-) - you can perfectly access your dev app from the network. > So as a > suggestion for future TG releases, it might be convenient for some > some situations to be able to enable Autoreload in prod config, even > if it's not the default behavior. (And/or to enable use of a real URL > during dev config.) > In fact, you're perfectly free to do anything you want with your dev and prod configs : configurations provided are just templates which most users will find usable in stock state. It shouldn't be too hard to add autoreload features to your prod deployment by yourself if you want it that much ;) >> 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? >>> >> This is not related, as this is a pure unix question. A tool like nohup >> will do the trick, but several alternatives exist. >> > > Ok, thanks, I can look into such approaches from a unix perspective. > But also perhaps as a future suggestion for TG it might be nice for > non expert users for TG to provide some start and stop scripts to do > this, similar to what Apache Tomcat provides. When I was developing > in Tomcat last year I was able to have the web app keep running my > terminal session without needing to delve into lower level unix to do > this. Probably most TG users never need this, but just mentioning it > as a suggestion of something to consider. > Providing deployment scripts or not is a matter of taste, and I personally like better the TG way (you have complete control on your process, and can demonize it by yourself if you want). Just a note : what I suggested (nohup, and more generally process handling) is by no means "lower level unix", but rather basic usage any unix user should be familiar with. It is not very complicated, a lot of related documentation can be found on the net (or your man pages, or your info pages, or your system doc) and it will make your life really easier.
dom --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
