mercury

I have a fresh installed Ubuntu server 10.04. I followed the instruction on this page (https://github.com/pantheon-systems/mercury) to install Mercury. I am not sure which version it is. I am assuming its the latest one (1.2) . here's the instruction

apt-get install git-core
git clone git://github.com/pantheon-systems/mercury.git -b master /opt/pantheon
cd /opt/pantheon
python setup.py
apt-get update
bcfg2 -vqed

Hi everyone. I'm the author of the initial stackscript over on Linode.

First, I apologize for not updating everyone sooner, but I've been working two positions at work and have been extraordinarily busy since about December of last year.

As some of you may have seen, we've officially announced the creation of Pantheon Systems, Inc and our plans to deliver a Platform as a Service (PaaS) solution for Drupal. We're super-excited about this, and hope to solve a lot of the hard problems that surround the Drupal space in the next year.

However, it's not appropriate for a company to have a Drupal group, and the open-source work on this project continues with Pantheon Systems as a contributor. As such, we've decided to restore the group name to the original "Mercury".

Updates to the open-source/DIY script for setting up the Mercury stack will be coming in the next few weeks, as we work with Boztek and others to get something stable. After that we can start to think about new StackScripts for Linode, AMI's for EC2, and possibly a VirtuualBox image.

Are there other places you'd like to see Mercury available? Other questions you have about the transition? Feel free to post questions here and I'll do my best to answer.

I've got an issue with varnish on my mercury server. I have a site that is located outside of /var/www so I setup a new apache vhost for the site that points to it's proper location and configured it to run on port 8080. When I try to visit the site through varnish on port 80 the default site comes up instead of the site i am expecting. When I visit the site on port 8080 it works fine. Is there something I need to do to varnish to make it aware that the site is not in /var/www? Any help would be appreciated.

I've got an install of mercury 1.1 on an ec2 tiny ubuntu instance. All seems to be going fine, except apache solr. Solr seems to quit periodically. When I run a search on the drupal site, I get a message saying "drupal can't connect to apache solr". If I restart tomcat6, the search runs OK, but then fails again after about half an hour.

I had a look at the tomcat log files, here is the last line form /var/log/tomcat6/catalina.out


Feb 8, 2011 5:20:51 AM org.apache.solr.core.SolrCore execute

I'm trying to create an AMI from my running Amazon instance. My running instance is a mercury 1.1beta which I initiated from the public Mercury 1.1beta public AMI.

I'm using this command where 123456789123 is my actual Amazon user ID:

$ sudo ec2-bundle-vol -d /mnt/amis -k /mnt/ids/pk-*.pem -c /mnt/ids/cert-*.pem -u 123456789123 -r i386

I get the following:

Copying / into the image file /mnt/amis/image...
Excluding:
/sys/kernel/debug
/sys/kernel/security
/sys
/var/log/mysql
/var/lib/mysql
/mnt/mysql
/proc
/dev/pts
/dev
/dev
/media
/mnt

Our use case for our Mercury install has suddenly changed in our architecture and it has been determined that we will use SSL only traffic.

I've been trying to read up on how to get Varnish to interact with HTTPS. It appears, to my dismay, that Varnish does not play well with SSL.

I've found this thread:
Enforcing SSL Behind AWS Load balancer
http://groups.drupal.org/node/115284

and this blog post
Setting up Pressflow and Varnish to work with HTTP and HTTPS
http://singlemindconsulting.com/blog/christoler/2010/8/setting-pressflow...

Background in Linux: not much... used Ubuntu & Mint as desktop for a year or so
Drupal dev: couple years now, part time

Currently have my sites (just 2) on a shared hosting situation and want to move to where I'll have more control over performance. Since I love piling on modules in my Drupal installs, query load (I don't know all the proper terms for these things) is heavy.
Research led me to Linode and then to Mercury... and Pantheon. So there wd be easier ways to get my sites up at Linode, but promise of much better performance = irresistible. (Want to pile on more Drupal modules!)

Hello,

I've had a Mercury 1.1beta setup at Amazon using an AMI for a few months now. Since this box has been a development box, I hadn't bother to setup automatic snapshots. I was doing them manually from time to time.

Now that we are getting closer to something that will become production, I would like to enable automatic snapshots.

At the time I setup my first instance, which happens to be Instance Store - I followed the document "Set up EBS for Mercury" which describes how to attach an EBS volume and copy www-data and MySQL data to the attached EBS volume.

We’re running into an issue sending duplicate notifications to our users using the Notifications module on our Mercury Pressflow implementation. The duplicate messages are identical save one thing- the [node-url] token is being replaced with ‘default’ in one of the messages. All the other tokens in the message are being replaced correctly.
The duplicate emails do not happen consistently, maybe 10-15% of the notifications sent out, however a duplicate message always has the proper url & the ‘default’ url.