- Timestamp:
- 08/09/09 09:37:15 (3 years ago)
- Files:
-
- 1 modified
Legend:
- Unmodified
- Added
- Removed
-
enpraxis.educommons/trunk/enpraxis/educommons/MIGRATION.txt
r566 r568 1 1 =================================== 2 Migrating to eduCommons 3.2.1- rc22 Migrating to eduCommons 3.2.1-final 3 3 =================================== 4 4 … … 13 13 14 14 15 Migration of eduCommons 3.1.1-final to 3.2.1- rc215 Migration of eduCommons 3.1.1-final to 3.2.1-final 16 16 -------------------------------------------------- 17 17 18 The migration eduCommons from version 3.1.1-final to version 3.2.1- rc218 The migration eduCommons from version 3.1.1-final to version 3.2.1-final 19 19 includes the following: 20 20 21 21 1. Pre-migration of Data.fs in version 3.1.1-final 22 22 23 2. Movement of Data.fs file to a new 3.2.1- rc2instance23 2. Movement of Data.fs file to a new 3.2.1-final instance 24 24 25 3. Migration to the eduCommons 3.2.1- rc2instance25 3. Migration to the eduCommons 3.2.1-final instance 26 26 27 4. Export/Import of eduCommons site to a new 3.2.1- rc2instance27 4. Export/Import of eduCommons site to a new 3.2.1-final instance 28 28 29 29 5. Final steps … … 70 70 71 71 72 Movement of Data.fs file to a new 3.2.1- rc2instance72 Movement of Data.fs file to a new 3.2.1-final instance 73 73 ------------------------------------------------------ 74 74 75 75 For this step, you will move the Data.fs file from the old instance to 76 the new instance. First of all, install an eduCommons-3.2.1- rc276 the new instance. First of all, install an eduCommons-3.2.1-final 77 77 instance using the installations instructions found in [new instance home]/eduCommons/docs/. Stop both sites. Then 78 78 copy the Data.fs file from the var directory of the old site to the … … 83 83 84 84 85 Migration to eduCommons 3.2.1- rc2instance85 Migration to eduCommons 3.2.1-final instance 86 86 ------------------------------------------------ 87 eduCommons 3.2.1- rc2 uses the portal_setup tool to perform the necessary upgrade from 3.1.1 to 3.2.1-rc2. Due to the fact that eduCommons and it's dependencies were moved to python eggs, we must start with a new eduCommons site. The migration script will then copy and past content and relevant settings to the new installation:87 eduCommons 3.2.1-final uses the portal_setup tool to perform the necessary upgrade from 3.1.1 to 3.2.1-final. Due to the fact that eduCommons and it's dependencies were moved to python eggs, we must start with a new eduCommons site. The migration script will then copy and past content and relevant settings to the new installation: 88 88 89 89 1. Navigate to the root of your ZMI instance and create a new eduCommons site called eduCommons321 90 2. Open your new 3.2.1- rc2eduCommons site in the ZMI. (click educommons Setup, then click Zope Management Interface.)90 2. Open your new 3.2.1-final eduCommons site in the ZMI. (click educommons Setup, then click Zope Management Interface.) 91 91 3. Navigate to portal_setup 92 92 4. Press the 'Upgrades' tab … … 96 96 97 97 98 Export/Import of eduCommons site to a new 3.2.1- rc2instance98 Export/Import of eduCommons site to a new 3.2.1-final instance 99 99 -------------------------------------------------------------- 100 100 … … 102 102 103 103 1. Navigate to the root of your ZMI instance 104 2. Select the checkbox next to your new 3.2.1- rc2eduCommons site104 2. Select the checkbox next to your new 3.2.1-final eduCommons site 105 105 3. Press Import/Export 106 106 4. If your production environment is on the same server as your migration environment, choose 'Save file to server', else
