Monday 29 March 2004 10:46:20 am
Hi, I think one of the problem is that when you use the installer, it affects your server setup, because you are installing the web server, the database server ,etc Beside that, when using the installer you will end with a pre-defined server setup: paths, server settings, etc,etc In production environments hardly you will need this kind of installation, because a production server is supposed to have its web server, and database server previously installed and tuned, so installing that stuff again is useless and can affects the server normal operation Ultimately you can consider EZPublish, as a collection of dir and files stored under some main directory at your server
So to move your installation the only thing that you actually need is to copy or move that set of files to the new location keeping the proper dir and files permissions at the new server
You will also need a database backup, tipically a .SQL file, that can be obtained by a DB Server dump command (i.e mysqldump yourdatabasename -r yourbackup.SQL
), it will contain the database structure and data
So beside copying the dir and files, the only thing that you will need is to import your .SQL file to the database server available at the new server (i.e mysql yourdatabasename < yourbackup.SQL
) Of course, you may also need to change some settings at settings/..., but it has nothing to do with using an installer setup or a distribution setup
Lazaro
http://www.mzbusiness.com
|