5

If you know how to create a production or development server for EE2, you can create a staging server... if you don't know how to create a development or production server then go find that out first. The challenge with database driven CMS's however is not the servers, it is the database that drives the CMS. Before you can push changes that include any ...


3

Ultimately it comes down to your hosting company and how much control they have over mapping the domain's web root. I'd ask your host if you can re-map the production domain to point to /public_html/public. Same with your development domain, have it mapped to dev_html/public. So your setup will look like this: dev_html system public public_html system ...


2

First thing is checking your config.php and database.php. They can be found in /system/expressionengine/config. Check your database credentials. In the config.php file check the file paths and turn error reporting on. Also, there might be an alternative config solution such as config bootstrap or master config. If that's the case, update those files with ...


2

I'll elaborate more on my comment to answer the poster more fully... There isn't a reliable, solid mechanism (especially automated) that I've come across that can safely migrate content forwards onto a live site - especially if you have living data (membership, commenting, forums, etc). If considering this, also remember environment configs and entry hit ...


2

This is what the assign_to_config array in your main index.php file is for (assuming you're not using something like FocusLab Master Config, which makes multi-environment really easy). If you don't want to use that approach, the quick way is to just crack open your index.php file, scroll down to the bit where assign_to_config gets set, and create some global ...


1

You might want to consider this Bootstrap file from Ben Parizek (originally from Leevi Graham). It allows for Local, Development (Staging) and Production (Live) environments. You can set different environment variables and database connections for each. Works well if you're using (and you should be) a code versioning system, and the some kind of deployment ...


1

Another option, though not ideal, would be to put a conditional in the index.php and admin.php files: switch ($_SERVER['HTTP_HOST']) { case "www.example.com" : $system_path = "../system"; break; case "dev.example.com" : $system_path = "../system_dev"; break; default : $system_path = "../system"; break; }


Only top voted, non community-wiki answers of a minimum length are eligible