- Timestamp:
- 08/09/09 01:43:29 (3 years ago)
- Files:
-
- 1 modified
Legend:
- Unmodified
- Added
- Removed
-
enpraxis.educommons/trunk/enpraxis/educommons/MIGRATION.txt
r522 r566 1 1 =================================== 2 Migrating to eduCommons 3.2.1 2 Migrating to eduCommons 3.2.1-rc2 3 3 =================================== 4 4 … … 13 13 14 14 15 Migration of eduCommons 3.1.1-final to 3.2.1 15 Migration of eduCommons 3.1.1-final to 3.2.1-rc2 16 16 -------------------------------------------------- 17 17 18 The migration eduCommons from version 3.1.1-final to version 3.2.1 18 The migration eduCommons from version 3.1.1-final to version 3.2.1-rc2 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 instance23 2. Movement of Data.fs file to a new 3.2.1-rc2 instance 24 24 25 3. Migration to the eduCommons 3.2.1 instance25 3. Migration to the eduCommons 3.2.1-rc2 instance 26 26 27 4. Export/Import of eduCommons site to a new 3.2.1 instance27 4. Export/Import of eduCommons site to a new 3.2.1-rc2 instance 28 28 29 29 5. Final steps … … 70 70 71 71 72 Movement of Data.fs file to a new 3.2.1 instance72 Movement of Data.fs file to a new 3.2.1-rc2 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 76 the new instance. First of all, install an eduCommons-3.2.1-rc2 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 instance85 Migration to eduCommons 3.2.1-rc2 instance 86 86 ------------------------------------------------ 87 eduCommons 3.2.1 uses the portal_setup tool to perform the necessary upgrade from 3.1.1 to 3.2.1. 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-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: 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 eduCommons site in the ZMI. (click educommons Setup, then click Zope Management Interface.)90 2. Open your new 3.2.1-rc2 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 instance98 Export/Import of eduCommons site to a new 3.2.1-rc2 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 eduCommons site104 2. Select the checkbox next to your new 3.2.1-rc2 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
