Tuesday 16 June 2009 1:04:32 am
As stated above, installation to a new server via file copy and db import should not be too hard. Some tips: - put ezcomponents in lib/ezc instead of using the version that is installed via pear, even on your dev machine. This makes it easier to later move the self-contained installation to a different server. If taht is not the case now you can eg. download the version of eZP that comes with ezc inside and copy the lib/ezc dir into your existing installation. - you will (of course) need to alter the config. for db access in an override of site.ini - remember to carry over var/storage and var/mysiteaccess/storage - you can clear all cache and log files manually (or omit importing them) - take care about siteaccess: what rules do you use to determine siteaccess: is it hostname or url - based? If it is hostname based, chances are you will not be using the correct siteaccess when using the hostname of the new server, and as such you will be missing login permissions in the roles-and-perms admin interface. You will need to fix your site.ini in override, again - last but not least, look at var/log dir on the new server, and make sure there are no error messages about not being able to write cache files because of filesystem permissions
Principal Consultant International Business
Member of the Community Project Board
|