I spent some time adding Python/WSGI support to CloudFoundry over the weekend...in general, this project is extremely well designed and SOLID. Almost all of the headaches involved with, for example, adding Django support, stem from Django's conventions and requirements (something I'm not a stranger to).
I'm really looking forward to the future of CloudFoundry.
The thing that I don't understand is that the problem of getting frameworks to work consistently with web servers has already been solved by the Rack project. For the life of me, I can't understand why CF doesn't simply look for a config.ru file and pass it to Thin and be done with it.
Do you guys have a timeline on that? As I said, I don't mind sitting down and trying to knock it out but schedule wise it won't be in the immediate future. If you guys are already on it (as in someone is currently working on it), I can just wait till the first feature branch on github and go from there.
Yeah I was a bit confused by this as well. I haven't looked at the rails code in vcap yet but you're right in stating that this is a solved problem. I think they were going for something a little more generic for code reuse reasons? I plan on sitting down with the code in earnest and helping flush out the rack/sinatra stuff to be better tuned for that use case.
I'm really looking forward to the future of CloudFoundry.