Blog

Erlang strings are painful

Oh it’s so true. The pain is super apparent, especially when trying to parse configuration files. The traditional way to parse a configuration file that is not in the erlang format can be pretty hard to do. For instance, for beehive, the application configuration template looks like:

In this new series on my blog, we’ll look at a few different deployment frameworks (as alternatives to Beehive).

VMWare just released their new CloudFoundry framework to the Open-Source world. Obviously, I’m pretty interested in application deployment, so this clearly piqued my interest.

After upgrading to Snow Leopard, I found my os_mon erlang application exploded in a very ugly error message.

Introduction

Beehive is an open-source application deployment implementation that uses technologies like squashfs, erlang and ruby. It aims to provide a simple, easy application deployment platform. This post will go over the router portion of Beehive.

Architecture

So you have your killer erlang application that possibly could make you millions, but it was written in a test environment. Shoot, how do you change that “on the fly” at the application runtime? There are a many different ways this can be accomplished. This post will go over the basics of this typical issue.