Project Mercury Documentation
We are still pulling together comprehensive documentation for this project. This page should help in the short term. Please feel free to edit our wiki pages and contribute your own HOWTO content!
Posts In "Documentation"
- Drupal sandbox for Linode StackScript
- Linode StackScript for Ubuntu 10.04 and Mercury 1.1 available
- Scaling Plan for Novice
- How to try out Pantheon quickly and easily (on a linode slice anyway)
- SO MANY PASSWORDS REQUIRED FOR PANTHEON SETUP / LETS MAKE IT SIMPLE AND CLEAR HERE
- Ubuntu 10.04 Step-by-Step for Multi-Drupal Instances Same Server (not Multi-site)
- Tomcat tweak for ApacheSolr powered search on non English words
- Step-by-step: Installing Project Mercury 1.1 (Beta) on Centos 5.5
- Rackspace Setup on Lucid
- Step-by-step: Installing Project Mercury 1.1 (Beta) on Ubuntu Lucid
- Drush make file for mercury?
- Upgrading from Mercury 1.0 (or Mercury 1.1-Beta) to Mercury 1.1
- How to use the new templating system in Mercury 1.1
- Install Aegir In Mercury - New Installation
- Step-by-step: Setting up Project Mercury 1.0 (Varnish, Apache, APC, Memcached and Solr) using BCFG2
- Installing Your Drupal Project On Project Mercury
Step-by-step: Installing Project Mercury 1.1 (Beta) on Ubuntu Lucid
Last updated by innovationcreation on Sun, 2014-11-16 21:22
Here are step-by-step instructions for building Project Mercury 1.1 (BETA!!!) on a fresh Ubuntu Lucid server using the configuration manager BCFG2. Project Mercury is known to work on AWS, Rackspace, RackspaceCloud and Linode. We have AMIs of Mercury 1.1 Beta for AWS EC2 (see: http://groups.drupal.org/node/71943) and (soon) a Linode script for Mercury 1.1 (both on Ubuntu Lucid).
6/1/10: Updates for multi-site support
7/12/10: Added EBS-boot and hudson support
Step-by-step: Installing Project Mercury 1.1 (Beta) on Centos 5.5
Here are step-by-step instructions for building Project Mercury 1.1 (BETA!!!) on a fresh Centos 5.5 server using the configuration manager BCFG2. Project Mercury is known to work on AWS, Rackspace, RackspaceCloud and Linode. We'll have Centos images up on AWS soon.
Voxel.net has official Mercury 1.1 images available using 64-bit Centos (VSE) 5.2!
Read moreMigrating Your Existing Site to PANTHEON
So long as you are following best practices, migrating an existing Drupal site onto PANTHEON is not very difficult. This page will walk you through the steps you need to take to deploy an existing site onto the base installation. If you are interested in deploying from version control, please see deploying from VCS with PANTHEON.
Read moreDeploying From Version Control Within PANTHEON
Congratulations! If you're reading this, you're doing things correctly. In the modern era of the web, we don't want to be making edits directly on a live site. It's just too risky, and it starts getting really tricky when you're working with a team. Deploying from version control solves these problems.
If you already have your own system or method of deploying a whole Drupal installation, feel free to take over all of /var/www on your PANTHEON server. You should base your application on Pressflow and include the ApacheSolr, Varnish and Memcached modules as well as the necessary settings.php configuration to utilize these features. For more on this, see the settings and module configuration page.
However, if you don't have an existing deployment system, but you do keep your code in version control (e.g. SVN) you can easily integrate with the provided Pressflow installation — which is itself checked out from Launchpad for easy updating — by following these instructions:
Read moreDrupal Settings and Module Configuration for PANTHEON
Even though the PANTHEON server "stack" is already tuned to run Drupal as fast as possible, if your application doesn't know how to take advantage of the environment you won't see the breakthrough performance. This page describes the few key steps you need to take to insure that your Drupal application is ready to blaze.
Read moreUpgrading from Mercury 1.0 (or Mercury 1.1-Beta) to Mercury 1.1
Last updated by adrianrf@gmail.com on Tue, 2010-06-29 06:33
We know some folks are going want to upgrade their mercury servers from 1.0 or 1.1-Beta to 1.1 once it's released, so we've written instructions on how to do this.
Read moreMercury's Template system
We've updated how we use BCFG2's template system so that making changes to your mercury server is easier. All tuneable configs are now located in /etc/mercury/server_tuneables. Changes made to the variables in this file will be applied (and not overwritten) by BCFG2 whenever it updates it's configuration.
When you make changes to the tuneables, remember to have bcfg2 update the environment:
bcfg2 -vqed #update the server environment6/22/10: updated with new default settings.
Read moreusing BCFG2 to manage Pantheon
To support our efforts to make Pantheon and all it's parts available on multiple operating systems and virtual private servers, we're implementing BCFG2 (http://trac.mcs.anl.gov/projects/bcfg2) for configuration and management. We've placed BCFG2 configuration files for Mercury on Ubuntu Jaunty 32 bit server in our launchpad project (https://launchpad.net/projectmercury) for folks to start using.
Read moreInstructions for setting up multi-site on Mercury
These instructions are for any Mercury 1.1 Beta created after 6/1/10 (including the Mercury 1.1 Beta2 AMIs we released on 5/29/10).
Read moreSetting up EBS for Mercury [Beta]
Last updated by jlmeredith on Thu, 2010-11-18 10:32
Once you've followed the steps outlined for installing your site on Mercury you'll then want to take your site to the next level using Elastic Block Store. This is going to keep your MySQL database(s) persistent should your server instance crash. Also make it easy to replicate data for testing etc.
Read moreInstall Aegir In Mercury - New Installation
===============================================================================
Updated... for Latest Mercury 1.1 release.
However it died after verifying the first Aegir site; I dont have the time to find out why at the moment so please use the previous revision which is known to work with Mercury 1.0 and the latest Aegir. I couldn't revert this wiki page to a previous date so this note will have to suffice.
===============================================================================
===============================================================================
Read moreAdding Munin to Mercury
I have seen Munin mentioned as a desirable component in Mercury, and I'd like to add my vote. I've found it a really useful diagnostic tool.
I just went through the process of installing it using this tutorial: http://www.debuntu.org/how-to-monitoring-a-server-with-munin
Very straightforward. The only changes I needed to make where in the VirtualHost configuration for the monitoring site - I had to a) change the *:80 to *:8080 to accommodate Varnish, and b) use AuthUserFile rather than AuthDigestFile.
Read moreRunning Drupal/Pressflow on Lucid.
As many of you know, Ubuntu Lucid shipped with PHP 5.3 which is incompatible with many Drupal 6 modules. The solution the Mercury team decided on was to pin PHP to 5.2 until the situation with 5.3 was resolved. Mercury 1.1 has this built in.
We've added all php5 packages to the file and are hosting it here: http://pantheon-storage.chapterthree.com/lucid
6/18/10 - found a bug and update the above file and the list below (for some reason, changing php5-imagick, php-apc and php5-memcache to karmic-updates caused it to fail)
6/15/10 - added updates from http://groups.drupal.org/node/75003 (view that page if you're using aptitude rather than apt-get)
Tomcat tweak for ApacheSolr powered search on non English words
Search on Mercury provided by ApacheSolr and hosted in tomcat. Tomcat is running on port 80. When a request contains UTF-8 characters there are percent encoding and Tomcat can't deal with it by default. See : http://wiki.apache.org/solr/SolrTomcat#URI_Charset_Config
Quote :
If you are going to query Solr using international characters (>127) using HTTP-GET, you must configure Tomcat to conform to the URI standard by accepting percent-encoded UTF-8.
Edit Tomcat's conf/server.xml and add the following attribute to the correct Connector element: URIEncoding="UTF-8".
Read moreConfiguring Varnish to make it work with language negociation
Drupal comes with a language negociation (D6: admin/settings/language/configure). One of the options is "path prefix with language fallback": If a suitable prefix is not identified, the display language is determined by the user's language preferences from the My Account page, or by the browser's language settings. The latter means it will look at Accept-Language in the http request and return the preferred language. I would like this still to work, together with Varnish cache.
Read moreConsistent EBS Snapshots for RAID arrays or single volume with Mercury
This wiki describes setting up consistent snapshots for EBS. It works with RAID arrays and a single volume. It also can be automated to run on a cron job.
Step 1: EBS Consistent Snapshots Installation
Instructions for installing ec2-consistent-backup can be found here: http://alestic.com/2009/09/ec2-consistent-snapshot.
Set-up access to Alestic PPA
codename=$(lsb_release -cs)
echo "deb http://ppa.launchpad.net/alestic/ppa/ubuntu $codename main"|sudo tee /etc/apt/sources.list.d/alestic-ppa.list
Ubuntu 10.04 Step-by-Step for Multi-Drupal Instances Same Server (not Multi-site)
Notes:
As of 10.9.2010, Does not work. For some reason will get a WSOD if cron runs twice in a row without the site being hit.
As of 10.8.2010: (later in the day!) Seems to be working, get a white screen of death, run update.php from the browser
As of 10.8.2010: I am sure this document will need to change, but this is where I am at currently with this install.
My Goal is to have two or more Drupal Installs with Pantheon, on Ubuntu 10.04.
I want my document root to be /var/www/www.example.com/htdocs/
Read more