Some time ago I described the steps I used to add Perl as a simple runtime and framework to Cloud Foundry. Since then many changes have taken place in Cloud Foundry and those steps no longer work.
I now have something that works as of 30 August 2012. To see the changes go to my github repository and view the changes to vcap, vcap-staging, stager, and cloud_controller. Note that the recent refactoring of Cloud Foundry means that instead of isolating changes to one repository, we now make changes to four repositories.
Of course, there may be more efficient ways of doing this, but this is what I’ve found to work for me today!
Update 1: It wasn’t much work to update the earlier work on Cog/Aida. It involved similar changes to vcap, vcap-staging, stager, and cloud_controller.
Programming Gems (on GemStone) 
3 comments
Comments feed for this article
August 30, 2012 at 12:46 pm
Andy Burnett
Hi James,
Are we any closer to having Gemstone officially supported on Cloud Foundry. I am itching to use the service, but I really want something that ‘just works’. Any thoughts?
August 31, 2012 at 9:27 am
James Foster
Are you referring to CloudFoundry.org (the open-source project)? If so, then I should have a fork of the code working with GemStone soon (it was working a few months ago, but things have changed significantly).
Or are you referring to CloudFoundry.com (the VMware hosting site)? If so, then we are no closer because no effort has been made to convince management that the market for GemStone is similar to the market for MongDB.
Do you think that there would be sufficient demand for a hosted GemStone service to make a compelling business plan?
August 31, 2012 at 10:47 am
Andy Burnett
What I am after is Gemstone as a Service. I can see your point. Without sufficient users the return on making that run on cloudfoundry.com would be too low. I was just hoping that because it was a VMWare product, they would naturally include it within their hosted service.
Oh well, off to find another way of doing it 🙂