Closed
Bug 521211
Opened 16 years ago
Closed 16 years ago
copy over production database over to stage
Categories
(Websites Graveyard :: spreadthunderbird.com, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: graphicsguru, Assigned: gozer)
References
()
Details
gozer copy over production database over to stage
Updated•16 years ago
|
Assignee | ||
Comment 1•16 years ago
|
||
And you want that to squash the current staging database or to have it copied as a separate database on staging ?
Comment 2•16 years ago
|
||
@gozer
Can we have the stage server just running the latest production database.
I'll then re-enable the new theme and given an account that is currently only on production administrative access
Best, Paul
Assignee | ||
Comment 3•16 years ago
|
||
$> mysqldump -h production --ignore-table=drupal.cache --ignore-table=drupal.cache_block --ignore-table=drupal.cache_content --ignore-table=drupal.cache_filter --ignore-table=drupal.cache_form --ignore-table=drupal.cache_menu--ignore-table=drupal.cache_page --ignore-table=drupal.cache_update --ignore-table=drupal.cache_views --opt drupal | mysql drupal
Done, stage doesn't look very happy as a side-effect. Find me on IRC if you need assistance
Assignee | ||
Comment 4•16 years ago
|
||
Cleared cache and things look better.
Comment 5•16 years ago
|
||
@gozer Works perfectly!
Thanks Paul
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Updated•12 years ago
|
Product: Websites → Websites Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•