Move application to live site.

There are 2 options, both will allow rpms 1 and 2 to be on the live server at the same time.

1. Option one will make rpms 2 immediately available with the newest data. The fall back is to use rpms 1 instead.
2. Option two is to have rpms 2 installed on live with old data, and continue using rpms 1. This will allow testing on live before using new data, but will delay using rpms 2.

Option One

This sequence is to begin using edemo rpms 2.0 immediately

1. ... Schedule edemo downtime...
2. Get sql dump with newest data in old db from edemo (this will be the db revert file if needed)
3. update/run dump on idemo.
4. Run sql to create new db on idemo.
5. Run php data migration with newest data in old db to new db.
6. Validate new db, functionality, and new data on idemo.
7. Get sql dump from idemo with new db and new data.
8. Add new files to edemo
9. Move db dump to edemo.
10. Validate db and functionality.
11. ... End scheduled edemo downtime...
12. Now you can begin using rpms 2 or rpms 1.

Option Two

This sequence is to continue using rpms 1, while testing rpms 2

1. Get sql dump from idemo with ONLY new db and old data (do not dump old db).
2. Move db dump to edemo to add new db with old data.
3. Add new files to edemo
4. Validate db and functionality with older data.
5. You can continue to use rpms 1, and only test on rpms 2.

Start this sequence to begin using rpms 2

1. ... Schedule edemo downtime...
2. Get sql dump from edemo
3. Update/run dump on idemo.
4. Remove all records from new db on idemo.
5. Run php data migration from old db to new db on idemo.
6. Validate db, functionality and new data on idemo.
7. Get sql dump from idemo, update on edemo.
8. ... End scheduled edemo downtime...
9. Now you can begin using rpms 2.