Using the Backup Module to move to remote server

[Darwin Web Design]

Hi,
I've developed a website on my localhost Wamp server and am now ready to move it to a remote server for my client (nervous).  I have read the forums about using the Backup Module.

The instructions say to:

- install the backup module (done)
- create the backup (done)
- install CMSMS on the new location (which is where my query lies).

Do I have to install the basic original CMSMS or can I just copy all of my CMS files from the site I've been developing?  I don't really understand how it works but if I just install the original one, will the backup module bring EVERYTHING across from the backup ie all the work on my new design, styles, settings, users etc etc?  Would there be anything extra I have to copy across from the local one to make sure it's EXACTLY the same. 

Thanks 

[tsw]

everything (except images and files uploaded) are in database which backup module will handle.

You can make new installation in new server or copy all the files there it doesnt really matter as those files will be the same.

(remember to clear cache from admin if you move your test files to the server)

hope this helps

[Darwin Web Design]

Thank you, that is very handy to know.

[fredt]

I'd say "you can copy all the files to the remote server" IF your web server software, php version & ini, directory structure, even OS will be exactly the same, even from the letters/resources to mount the web server root files.. (developing in a Virtual Server(s) cloning the customer environment can be very time&life-saver).

So I' rather say: you can make a new install, then the config (automatically setting up all paths, db connexion...), login in the admin using the install db, create 2-3 pages, setup the nice urls, check it's all ok from all browsers... then Restore the db from your backup. Or copy all your files, edit & check carefully include.php and config.php, so it has a chance to work... then pray & Restore the db.

All in all, I guess restoring on a fresh install is better if you haven't already experienced adjusting those config files - the fresh install will allow you to check/validate the install is OK (web server can have a different config, and two-three+++ other params...). I wouldn't recommend entering editing configs & starting debug if things go wrong... while delivering a product for a (nervous !) customer on a production server. Don't give the system a chance to reveal to the customer you ever doubt or hesitate...

[Dr.CSS]

How I do it.
And I might add to this that I will install all the same modules to the new install first so the data base has something to relate to.

http://forum.cmsmadesimple.org/index.ph ... 376.0.html

[Darwin Web Design]

OK, thanks it's settled then...

1)  Install from scratch
2)  Import the new database - will replace all modified templates, styles, content (as per Mark's backup instructions)
3)  Replace the uploads directory so it carries across the images/files (or maybe do this before installation, when uploading all the files?)

Thanks 
Regards
Eva