Update the staging sites with the latest sanitized copy of Drupal.org. Narayan started sanitzing a new copy this afternoon, so we should have new staging db

Comments

calebgilbert’s picture

Assigned: Unassigned » calebgilbert
rfay’s picture

Priority: Normal » Critical

IMO this is the most important task on our list right now so I'm setting it to critical. If we can get this done, we'll have a sane starting point. The problem with what we're doing right now is we have no idea where the existing DBs came from, so we can chase problems that we don't even know will be issues in the current db.

rfay’s picture

Title: Update staging sites with santized drupal.org » Update staging sites with sanitized drupal.org
rfay’s picture

Title: Update staging sites with sanitized drupal.org » Update staging sites with sanitized drupal.org database dump
calebgilbert’s picture

Status: Active » Fixed

This is done, so now the next issue along these line is Get permissions for all staging admins to restore/backup staging db

rfay’s picture

Status: Fixed » Needs work

You did all 10?

So let's figure out the correct sequence of events after a database update.

At a minimum we need to turn on the staging_drupal_org module to grant us all admin privs:

cd /var/www
./drush_everywhere.sh mm enable staging_drupal_org

And then we have to run update.php on all of them. I haven't been successful doing this with drush, but we should be able to do it now via the web interface.

Please note here any additional steps that have to be taken, so we can capture them all. We'll be doing this again.

calebgilbert’s picture

Leaving this ticket open for tracking purposes, but am planning to solve everything (e.g., getting new db in all staging sites) in http://drupal.org/node/632534 during the process of getting access/scripts done for all the redesign admins.

rfay’s picture

When site status changes, please update the staging site wiki: http://groups.drupal.org/node/36744.

Amazon’s picture

Status: Needs work » Fixed

Moving this to fixed. I think it's now being addressed here: http://drupal.org/node/632534#comment-2322564

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

Component: staging.drupal.org » Other