With great pride, and after six alpha-level releases, I'm announcing of our seventh iteration on the Project Mercury stack, finally baked enough to call "beta". This release is a milestone: our course is now locked in for the 1.0 release.
At this point, we know that many people are using the Mercury EC2 image (or the same stack) in production environments, and we've tuned this release conservatively to prevent it from breaking down under heavy load. We've also verified that the stack will work under a resource-constrained VPS (e.g. one with 1/4th the RAM of a small EC2 image), which gives us more confident that this configuration is stable.
You can find the EC2 image in the US and EU availability zones with the following manifests:
Thanks to all the people who have provided critical encouragement and feedback as we've developed this toolset over the past three months. Over 300 Mercury instances have been launched so far!
The next steps are zeroing in on 1.0 release, making the image available in other places (e.g. RackSpace Cloud, VMware marketplace, etc) and working to get a "hosted" version of it online through a number of partners.
More exciting news to come. Stay tuned, as always, and let us know what you're thinking about.
Working with Chapter Three was great! They understood the development workflow perfectly and accommodated our needs to handle the theming and IA of the site. Add to this the short timeline and last minute changes they put up with. One area that Chapter Three really helped was setting up the development environment for us. This has proved invaluable to managing the site and pushing new features.
Michael Shaver, Web Administer, Intel Moblin Case Study
Some instructions for installing your Drupal site on top of mercury are online here:
http://groups.drupal.org/node/33078