How to copy your Saurus CMS website
Moving or copying your website between the different servers or inside one server is quite simple process - this article will give you some general guidelines.
Having SSH access
1. Source site: Go to your website root directory and pack all files
$ tar -czpvf ../web_scripts.tgz * .htaccess
NB! it is common mistake not to include the file ".htaccess" into the package.
2. Source site: Create MySQL database dump
$ mysqldump -u username -p --opt database > web_db.dump
3. Move files "web_scripts.tgz" and "web_db.dump" to the destination directory
4. Destination site: Unpack files
$ tar -zxpvf web_scripts.tgz -C /your/website/root/directory/
5. Destination site: Import MySQL data into the new database
$ mysql -u username -p new_database < web_db.dump
6. Cleanup template's temporary files
$ rm -rf classes/smarty/templates_c/*
7. Check permissions - be sure that the following upload directories have write permissions on the web server:
- failid/ - files used for content management - ver3
- public/ - files used for content management - ver4
- shared/ - files used for content management - ver4
- classes/smarty/templates - Saurus API templates
- classes/smarty/templates_c - Saurus API compiled templates code
- classes/smarty/cache - Saurus API templates cache
NB! The files in the directories "failid/" (or "public/", "shared/" in ver4 ) and "classes/smarty/templates/"must be owned by webserver OR must be readable and writable for the webserver.
Having FTP access and phpMyAdmin
1. Source site: Copy all files from the website root directory to the destination directory.
NB! it is common mistake not to include the file ".htaccess" into the package.
2. Source site: Create MySQL database dump using phpMyAdmin.
3. Destination site: Import MySQL data into the new database using phpMyAdmin.
4. Cleanup template's temporary files. Delete all files in the directory "classes/smarty/templates_c".
5. Check permissions - be sure that the following upload directories have write permissions on the web server:
- failid/ - files used for content management - ver3
- public/ - files used for content management - ver4
- shared/ - files used for content management - ver4
- classes/smarty/templates - Saurus API templates
- classes/smarty/templates_c - Saurus API compiled templates code
- classes/smarty/cache - Saurus API templates cache
NB! The files in the directories "failid/" (or "public/", "shared/" in ver4 ) and "classes/smarty/templates/"must be owned by webserver OR must be readable and writable for the webserver.
6. Check configuration files - in version 3.x be sure that the file config.php is exactly the same in the following directories:
- / - website root directory
- editor/
- admin/
Version 4 includes only one instance of config.php file.
Notice: If your website URL changed during moving/copying the website then you should contact your reseller for license issues.
RSS