requesting access to scratchvm

Hi, we are trying to make it so the staging sites don't require local access. I'll work with Andrew to create the tools so you can update modules and push your theme automatically to the site.

Kieran

But then there's the other question: What does scratchvm have to do with the staging sites?

If this is about the staging sites, the machine is stagingvm, and the technique to deploy modules and themes is at http://groups.drupal.org/drupalorg-redesign-implementers/code-repository.

In order to theme association.drupal.org sections to use the new Blue Cheese theme Linnovate needs access to association.drupal.org which has confidential information like passwords to our affiliate accounts, contact and payment information in CiviCRM. So it's best to isolate this association.drupal.org staging site where it is, and replicate what you've done with module and theme check-out so the Linnovate team can do their work on the scratchvm server.

I can get you access to scratchvm, but don't know if this is still outstanding or if you actually need access to stagingvm. What was the resolution here?

The prefered resolution is to checkout out two directories from SVN onto ScratchVM in the d6-association.drupal.org directories.

Zohar, could you provide us with a theme and module directory to checkout?

Then we can check them out every 5 minutes via cron.

Kieran

We no longer need this; I'd assumed they needed somewhere to test changes before committing, but a cron job is sufficient.

I've got it set up as an svn:externals, and have a crontab for my own user set to do an svn up every minute.