Difference between revisions of "Website 3.0 Migration Plan"
Marc.maier (talk | contribs) |
Marc.maier (talk | contribs) (→Go Live) |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 5: | Line 5: | ||
In order to refresh the test enviroment, we need to: | 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. | # Copy the test database to backup database so we have backup of the changes we have made to the test environment. | ||
| − | |||
| − | |||
# Copy all files from production environment to the test environment without deleting the current files. | # Copy all files from production environment to the test environment without deleting the current files. | ||
| − | # | + | # Script changes to tables in the production database that have been made. |
# Apply scripted changes to the test database. | # Apply scripted changes to the test database. | ||
# Apply manual changes to the test enviroment via admin interface. | # Apply manual changes to the test enviroment via admin interface. | ||
| + | The following tables need be copied: | ||
| + | * ccc_acy* | ||
| + | * ccc_akeeba* | ||
| + | * ccc_contact_details | ||
| + | * ccc_core_log_searches | ||
| + | * ccc_jev* | ||
| + | * ccc_menu* | ||
| + | * ccc_messages* | ||
| + | * ccc_version (does not work) | ||
| + | * ccc_content (only new content) | ||
| + | |||
| + | We need to use these settings: | ||
| + | * Data only | ||
| + | * Truncate table | ||
| + | * Maximum lenght: 5000000 | ||
| + | |||
| + | = Migration Plan = | ||
== Up To Two Weeks Before Go Live == | == Up To Two Weeks Before Go Live == | ||
Refresh test database with changes from production as described above every two weeks. | Refresh test database with changes from production as described above every two weeks. | ||
| Line 19: | Line 34: | ||
== Go Live == | == Go Live == | ||
| − | # Manually apply changes made in the last two weeks to test environment. | + | # Manually apply production changes made in the last two weeks to test environment. |
| + | ## Add noticesheets and newsletters | ||
# Backup production environment | # Backup production environment | ||
# Copy database and files from test enviroment to production. | # Copy database and files from test enviroment to production. | ||
Latest revision as of 21:03, 12 August 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.
- Copy all files from production environment to the test environment without deleting the current files.
- Script changes to tables in the production database that have been made.
- Apply scripted changes to the test database.
- Apply manual changes to the test enviroment via admin interface.
The following tables need be copied:
- ccc_acy*
- ccc_akeeba*
- ccc_contact_details
- ccc_core_log_searches
- ccc_jev*
- ccc_menu*
- ccc_messages*
- ccc_version (does not work)
- ccc_content (only new content)
We need to use these settings:
- Data only
- Truncate table
- Maximum lenght: 5000000
Migration Plan
Up To Two Weeks Before Go Live
Refresh test database with changes from production as described above every two weeks.
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 so we can test in a stable environment.
Go Live
- Manually apply production changes made in the last two weeks to test environment.
- Add noticesheets and newsletters
- Backup production environment
- Copy database and files from test enviroment to production.
- Perform checkout.
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
