Joe Freeman

Cloud Foundry - PaaS Each Cloud Foundry instance is a self contained environment (cloud) that is generally intended to be use as a black box application container. It is implemented in a virtualized environment that hides the actual virtual/physical topology from the deployer.  Service configuration, provisioning, log viewing and application deployment are done from outside the cloud through external tools.  Cloud services may use any ports or other resources and use unique usernames and passwords for each instance. Applications rendezvous with services, at run time, via declared service names. Cloud services are not visible outside the container.  All system monitoring must be done through log files, through code deployed in the application or through tooling provided by Cloud Foundry. Service tunneling, where you can bind to the data port of a provisioned service, will be added to Cloud Foundry in a post 1.0 release.  This blog article  describes how it will work and how you can

AMQP is an open protocol for Asynchronous message queueing.  The number one implementation for AMQP is RabbitMQ.   I normally run RabbitMQ on my Mac in a Linux/Ubuntu VM  but I recently got a new Macbook Air that's limited to 4GB.  I wanted to run RabbitMQ native on the Macbook Air instead of the Linux virtual machine to save space and give me better performance when running tcServer, RabbitMQ and STS on this slightly smaller machine.  Installation RabbitMQ is written in Erlang.  The Mac doesn't come with Erlang so you have to install it. You can use Macports or Homebrew per the Rabbit installation instructions .  I'm lazy so I used Rudix    Erlang-Solutions   which provides Erlang in neat Mac installation packages that put the files in  /usr/local /usr/bin. (The rudix version of Erlang went away over the weekend of 11/12/2011).  Download the img/package mentioned above and install it like any other .img file. Download RabbitMQ and unpack it into some worki