PDA

View Full Version : Moving to production server---pitfalls?


MichaelChristopher
24th of March 2005 (Thu), 15:34
I'll be moving the EE site I'm building from my localhost testing server to our hosting provider's (Interland's) server in a few days. I have some questions...

1. Will I be able to just ftp all the files and folders to my www root directory (after changing the appropriate urls, of course)?

2. How will I get the EE mysql database uploaded to my hosting provider's server and make it visible to EE? Sure wouldn't want to upload all the images again, as there are lots of different copyright year watermarks on them, and lots of description text.

3. I there a straightforward procedure for securing the site (I've changed the input folder's name)?

4. ...questions I haven't even thought to ask?

Thanks!!!

Pekka
25th of March 2005 (Fri), 05:37
Upload the folder/image structure as it is, and follow http://photography-on-the.net/forum/showthread.php?t=41046

You will need to create the empty database on new server before restoring the old one to it.

Database dump can be made with either EE Backup, or mysqldump utility that usually comes with mysql. If MySQL versions differ (especially when new mysql is older version) mysqldump is better choice as it can handle version differences.

MichaelChristopher
12th of April 2005 (Tue), 11:45
Pekka, I've been trying to mentally parse all this (new to me) mysql stuff, and I must be lots dumber than I thought. I've got a beautiful EE site all finished on my testing server (Apache2 server running in Windows XP), but I just cannot figure out how to get it uploaded. I've tried to figure out your instructions at http://photography-on-the.net/forum...ead.php?t=41046, but these steps elude me:

1. Get EE to backup the database into a separate db. The EE backup utility lists only one db in both the source and target db dropdows. Do I just backup to the same db?

2. Get mysqldump to run. I can't seem to do it from the mysql> prompt in the mysql command line prompt, nor does shell> run in my Windows command line window. I know that everybody is probably LOL right about now, but these chops I simply do not have.

Could you give me some step-by-steps in layman terminology? I've been pulling hair for over a week now.

Thanks again.

Pekka
12th of April 2005 (Tue), 12:40
You must use EITHER EE Backup OR mysqldump.

If you use EE Backup, you select the EE database from list and save the dump to a file. Then you upload with ftp the file to new server, into EE Backups ee_backup_files -folder and restore it from there using new server's EE Backup (ee_backup_prefs/preferences.php set up properly, of course).

If you use mysqldump you need to make a database dump in current server, for example

mysqldump --user username --password=password databasename --add-drop-table --lock-tables --add-locks -e -a -c > databasename.sql

If you use windows the easiest way is to find mysqldump program (usually in C:\mysql\bin ), open command prompt and drop the mysqldump.exe on to it and then add the parameters. When the dump is saved, you upload the dump into new server and using server's shell access you find the dump and give command:

mysql -u username -p databasename < databasename.sql

Mysql will promt for password and restore the dump after you give it.

The main difference between EE Backup and mysqldump is the EE Backup does not require shell access and that mysqldump can handle mismatched mysql versions better.

MichaelChristopher
14th of April 2005 (Thu), 15:39
All this somehow started soaking into my thick head and I got the site up yesterday (www.alliej.com).... THANKS!!!