A few more Pantheon 1.2 questions

Events happening in the community are now at Drupal community events on www.drupal.org.
zoon_unit's picture

I know you guys are still in development, but I'm happy to report that I'm zeroing in on a successful Pantheon 1.2 implementation. There are a few changes/adjustments needed for people who aren't using the strict Pantheon path layout. For instance, I'm configuring for several different domains which will eventually have live and dev versions. So I've set up new virtual host definitions.

I've successfully determined a workflow to import my existing sites manually into the Pressflow code, but have a few remaining questions holding me back:

1) The Solr path variable. This is set in the "sites-available" virtual host files, but what does it point to? For instance, the dev host file has "pantheon_dev" as the Solr path variable. If I want to enable Solr on a new site outside of the Pantheon layout, what should I change this variable to? I did a directory search and found "pantheon_dev" in three locations:

/var/lib/mysql/pantheon_dev
/var/lib/tomcat6/webapps/pantheon_dev
/var/cache/tomcat6/Catalina/localhost/pantheon_dev

If I wanted to setup a Solr site for "mysite.com" what must be configured where?

2) The memcache prefix. This is another value set as "pantheon_dev." If I want to enable a memcache prefix for "mysite.com" what needs to be done?

In advance, I apologize for getting you guys off track because I know you are focused on the getPantheon project, but if I can figure out these last two things, I should have a successful multiple site server running.

In fact, once done, if you guys would like, I'll try and write up a few customization instructions for people who want to beta test the Pantheon code. Documentation is my specialty.

Thanks again for the hard work. I'm using this as a huge training exercise, but I'm starting to appreciate the simplicity of the automated hosting environment you guys will be offering at getpantheon!

Comments

The variables that are set in

aaronlevy's picture

The variables that are set in the virtual host files are picked up in our pantheon.settings.php file (sites/default/pantheon.settings.php). So if you are setting up your own sites, it is easier to just set these values directly in settings.php

1.) In the case of the pantheon dev environment:
- The solr path variable refers to /etc/tomcat6/Catalina/localhost/pantheon_dev.xml
- In that file it sets the solr home to /var/solr/pantheon/dev

For a new site, you would need to create your own .xml file and change the solr/home path attribute. Then also create a new solr data directory at the solr/home path (a blank data dir can be copied from /opt/pantheon/fab/templates/solr)

If you feel ok about poking around in some code, you can see how it is provisioned during pantheon setup here: https://github.com/pantheon-systems/mercury/blob/master/fab/pantheon/pan... -- after these steps you would still need to set the drupal solr path variable to reflect your changes

2.) memcache prefix is just a unique string. So "mysite" works (as long as you haven't used that elsewhere). In pantheon the values used are "pantheon_dev", "pantheon_test", "pantheon_live".

Thank you, thank you, thank you

zoon_unit's picture

This Solr thing has been driving me crazy for days! That simple bit of info you provided was the key! This Solr layout was just different enough from the Solr "default" install provided in the Solr module help files to really confuse things.

I haven't looked yet (so it may already exist), but I assume that Hudson will have a provisioning script for setting up new Solr sites eventually.

This whole Mercury install has pointed out to me one of the classic issues with "black box" solutions. On one hand, there is no way I could have EVER setup a server with this much performance on my own. On the other hand, in order to maintain such a server, one needs to know what's going on in the "black box." (which is what I'm struggling to learn right now)

I know you guys are focused on the getPantheon project and it is fantastic that you are making this powerful solution available to the masses, but this also shows the critical importance of good documentation. Once the dust settles on this project (and assuming I figure things out) I'd be happy to volunteer some documentation for this excellent project.

Hey zoon unit if you ever get

AntiNSA's picture

Hey zoon unit if you ever get the occasion to break that down to an everydays man tutorial I would appreciate it!

Mercury

Group organizers

Group categories

Post Type

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds: