Thanks for the advice, Jon. But... I'm getting the idea the idea that this is next to impossible. You've even gone so far as to suggest registering a new domain :). I'm quite forgiving of Python web framework issues regarding deployment... but this is just getting silly.
> One option would be to put a static index.html at your root that > immediately redirects to a url where your TurboGears app is > published, so you go to "/" and it basically immediately redirects > you to "/blog" or whatever. This is the most promising option, and one I had considered. I'm being incredibly stubborn, though. I want this to work not only for myself, but out of principle! It should be possible with error-handler-404. > I am not sure where you got this. I don't know of any way to deploy > TurboGears applications that doesn't involve starting your > application process (which is a server). A socket file is just > another way for the web server to talk to your application process. Right, I'm not trying to get around having another process running. I'm trying to get around having some redundant ghost-server running on a random port on my server. (Also, anyone who browses directly to the proxy... any relative links that lead to static files wouldn't work since it would not check lighttpd. Making that port not accessible... more work.) Really the socket file thing is orthogonal to the request routing. I'll try the error-handler-404 approach with FastCGI from your site again without using a socket file this time. Does it work with TurboGears as presented, or do I have to make any changes? (I'm under the impression that the recipe was for use with vanilla CherryPy.) > It seems to me that you are making life a lot harder for yourself > than it needs to be by requiring that "/" be your TurboGears, and not > moving all your static content to a "/static/" directory or something > similar. I'm talking about thousands of files linked from all over the web (with my permission)... that would break a lot of stuff. Wouldn't putting some filter into CherryPy to look in a new directory when any incoming file request is received completely defeat the purpose of using lighttpd? I might as well just use the built-in server if that's the case... Thanks again. I'm ready to take an other shot at it! -- Brian Beck Adventurer of the First Order --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
