Difference between revisions of "Website 3.0 Migration Plan"
Marc.maier (talk | contribs) |
Marc.maier (talk | contribs) |
||
| Line 2: | Line 2: | ||
In order to make sure that we can prepare and test the website in the best way possible, we will refresh the test website from the production website every two weeks. In order for this to be viable we will impose a freeze on every major changes from the start to the project and impose a freeze on production changes from two weeks before launch. | In order to make sure that we can prepare and test the website in the best way possible, we will refresh the test website from the production website every two weeks. In order for this to be viable we will impose a freeze on every major changes from the start to the project and impose a freeze on production changes from two weeks before launch. | ||
| − | = Manual Steps = | + | == Refresh Process == |
| + | In order to refresh the test enviroment, we need to: | ||
| + | # Copy the test database to backup database so we have backup of the changes we have made to the test environment. | ||
| + | # Script changes to tables that been working on. | ||
| + | # Restore a copy of the production database to the test database. | ||
| + | # Apply scripted changes to the test database. | ||
| + | # Copy all files from production environment to the test environment without deleting the current files. | ||
| + | # Apply manual changes to the test enviroment via admin interface. | ||
| + | |||
| + | == Manual Steps == | ||
The following steps will need to be executed manually as part of the migration: | The following steps will need to be executed manually as part of the migration: | ||
* Go to ''Content > Article Manager > Options'' and set ''Linked Titles'' to ''No'' | * Go to ''Content > Article Manager > Options'' and set ''Linked Titles'' to ''No'' | ||
* Go to ''Extentions > Module Manager > Options'' and set the positions for ''Search'' and ''Smart Search'' to ''head-search'' | * Go to ''Extentions > Module Manager > Options'' and set the positions for ''Search'' and ''Smart Search'' to ''head-search'' | ||
| + | |||
| + | == Up To Two Weeks Before Go Live == | ||
| + | Refresh test database with changes from production as described above. | ||
| + | |||
| + | == Two Weeks Before Go Live == | ||
| + | |||
| + | Two weeks before, go-live we will institute a freeze on all production environment changes with the exception of the news section. | ||
Revision as of 07:54, 28 May 2015
Contents
Strategy
In order to make sure that we can prepare and test the website in the best way possible, we will refresh the test website from the production website every two weeks. In order for this to be viable we will impose a freeze on every major changes from the start to the project and impose a freeze on production changes from two weeks before launch.
Refresh Process
In order to refresh the test enviroment, we need to:
- Copy the test database to backup database so we have backup of the changes we have made to the test environment.
- Script changes to tables that been working on.
- Restore a copy of the production database to the test database.
- Apply scripted changes to the test database.
- Copy all files from production environment to the test environment without deleting the current files.
- Apply manual changes to the test enviroment via admin interface.
Manual Steps
The following steps will need to be executed manually as part of the migration:
- Go to Content > Article Manager > Options and set Linked Titles to No
- Go to Extentions > Module Manager > Options and set the positions for Search and Smart Search to head-search
Up To Two Weeks Before Go Live
Refresh test database with changes from production as described above.
Two Weeks Before Go Live
Two weeks before, go-live we will institute a freeze on all production environment changes with the exception of the news section.
