Upgrade Procedure

Upgrading a Silva production instance

This is the recommend procedure for upgrading a Silva site running in production. It uses a buildout tag with all desired configurations and product versions pinned down. For more info about using buildout see http://docs.infrae.com/silva/2.2/buildout.html.

1. Make a new buildout instance for testing the upgrade. You can do this ‘next to’ the current instance, or on another machine.
2. Copy the production Data.fs to the test instance with the newer Silva.
3. Upgrade the Silva root(s) in the copied Data.fs using the upgrade content button in Service Extensions.
4. Test all products and content, paying special attention to layouts, third party extensions not included in the core, and any custom code.
5. If necessary, adjust the buildout and run it again.
6. Fix and test problems and iterate until everything works. Make careful notes of all changes required, as you’ll have repeat all these steps.
7. Announce a ‘content freeze’: inform Authors and Editors about the upgrade, explaining that they won’t be able to do any work during the freeze (or if they do, it’ll be lost). You can also lock down Silva by changing rewrite rules in Apache.
8. Make a backup of the production Data.fs.
9. If you’ve been testing on another machine, make a new production buildout instance for the upgrade.
10. Copy the production Data.fs to the new instance.
11. Upgrade the instance using your notes.
12. Test all products and content.
13. Switch from the old production instance to the new production instance.
14. Announce the end of the content freeze.

Upgrading manually using tarballs

1. Download the desired Silva-all tarball, and any other product tarballs.
2. Extract the files into the Zope ‘Products’ directory.
3. Locate the UPGRADE.txt in the Silva product.
4. Follow the steps explained in UPGRADE.txt.