Excellent!!!!
I'm doing some efforts to make Pharo work in OpenShift (the cloud initiative of Red Hat) using the DIY (do it yourself) cartridge.
I started trying with Swazoo, but looks like SwazooServer is ignoring the ip address specified and binding to all interfaces (0.0.0.0) (Was an advice of a RedHat engineer).
Then tried with Zinc (thanks Sven by the off list help [1]) and seems to work now (Using #bindingAddress:).
I need still to polish a ton of things (the code itself, that not always work ok reading the RedHat environment (I'm doing via OSProcess), also I need to discover some random issues opening the authorized port, and finally develop the automation scripts to start/stop/restart). But I'm happy because is proved that the cog vm 2540 + Pharo 1.4 with Zinc works ok in OpenShift, as you can see at: http://zinc-garduino.rhcloud.com/
When I have more progress I will comment and document, my goal is that Smalltalk get included as an option in OpenShift (as currently are php, python, java, ruby). We are not second class citizens :)
I must also say a big thanks to several people of Red Hat because they have showed your interest in Pharo and helped me a lot.
The interesting part of OpenShift is that in the Express version 1.5 GB RAM and 3 GB disk space are availables for free!
Well, it's all for now, cheers!
[1] Sven, the latest mcz published today of ZincHTTPComponents seems to have some issues with the newest method #bindingAddress: (I don't have time now, but will try to reproduce in the next days if you need).
-- View this message in context: http://forum.world.st/Pharo-in-OpenShift-tp4560365p4560365.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.