Changes

'''New zarafa-7.0.x- and z-push-install/upgradescripts for SME8 <u>for testing</u>.'''<br>  These new scipts always take the default NEW-config-files from the zarafa.rpms (found in /usr/share/doc/zarafa/example-config/) and make SME-templates of these default config-files !  So, you will always have the newest templated config-files, even after upgrading to a new Zarafa-version with altered config-files !<br>

*'''New zarafa-7.0.x- and z-push-install/upgradescripts for SME8 <u>for testing</u>.'''<br>  These new scipts always take the default NEW-config-files from the zarafa.rpms (found in /usr/share/doc/zarafa/example-config/) and make SME-templates of these default config-files !  So, you will always have the newest templated config-files, even after upgrading to a new Zarafa-version with altered config-files !<br> There is even more integration with the SME-perlDB too.  (Most of the zarafa-config-keys can be set in the SME-perlDB !).<br>  

There is even more integration with the SME-perlDB too.  (Most of the zarafa-config-keys can be set in the SME-perlDB !).<br>  

*You can find a upgrade-path to Z-push 2.0 (tested with Zarafa 7.0.12 and Z-push 2.0.7).<br>

You can find a upgrade-path to Z-push 2.0 (tested with Zarafa 7.0.12 and Z-push 2.0.7).<br>

*For version 1.3 of the Webapp you need minimum zarafa 7.0.12.

For version 1.3 of the Webapp you need minimum zarafa 7.0.12.

 

= INSTALLATION of Zarafa 7.0.x on SME8 =

= INSTALLATION of Zarafa 7.0.x on SME8 =