Camera Icon

Got an event that needs shooting?  I've covered multiple events for marathon-photos.com and can capture the scenes & emotions that make your event unique.

Some samples of my own work are at Digital Formula on Flickr.

Wand Icon

Do you or your business need a website but you're unsure where to start?  Get in touch now and we'll get it sorted.

I focus on usable functionality & can setup smaller sites using Wordpress within hours of the order being placed.  Magic!

Globe Icon

So, you've already got a website but need help managing it?  I can help you.

Don't worry about knowing every single detail.  I'll find out the most important stuff and work with you to reach your goal, not someone else's.

 
Short URL
Warning: This article is older than 180 days and may contain inaccurate information.  Please use the information below at your own risk.

Move ExpressionEngine to a different server

Why move ExpressionEngine?

Good question! I run a local development environment at home so that I can simulate the production environment at ICDSoft as much as possible. When I make significant changes, however, this means I have to up and move my ExpressionEngine instance from my development server to my production server.

What do I need to do before beginning?

The process is actually fairly simple.  That said, always take the appropriate precautions before making any changes to a production environment, i.e. backup everything now including your existing file and the ExpressionEngine database.  After that it is highly recommended that you check your backup to make sure it's recoverable later.

Ok, I've backed up.  Now what?

You've backed everything up?  Good.  Here are the steps I followed to move my ExpressionEngine instance from my development server to my production server.

Prepare the database

  • Clear all ExpressionEngine caches.  DO THIS FIRST.
  • On the new server, if it doesn't exist already, create the database ExpressionEngine will use.
  • On the new server, if it doesn't exist already, create the database user that ExpressionEngine will use to connect to your database.
  • Dump the existing database to a backup file.  How you do this is up to you but I personally use phpMyAdmin to backup the database to a 'zipped' file.
  • Upload your database backup to the new database.
  • Confirm that your database user can connect to the ExpressionEngine database.

Prepare the ExpressionEngine files

  • Compress your existing site, probably to a ZIP file.
  • Upload the archived files to your production server.  
  • Uncompress the archived files into the appropriate directory.  Please note that most people simply FTP the files to the new server but I choose to do it this way as it's much quicker to transfer a single ZIP archive than it is to transfer the thousands of files ExpressionEngine uses one at a time.  I use a small PHP script to decompress the uploaded archive - you'll need to make sure your host allows this before it'll work for you.  Anyway, here's the source.
<?php
echo "Unzipping ...";
system("unzip my-site-archive.zip");
echo "Done!";
?>

Obviously you'll have to change my-site-archive.zip to the name of your uploaded archive ...

1 2 Next »

» Tags: expressionengine, ee, move ee, move expressionengine
DigitalFormula is an experiment in HTML5 and CSS3 design by Chris Rasmussen, an amateur/casual designer based in Melbourne, Australia. -37.813611 144.963056