2

I've started a big project and need to create some kind of staging area or testing environment, where I'm able to start off with developing the site and after launch will be able to use as the server where I'm able to add new features etc.

I've tried searching around, but haven't found a satisfying solution yet.

So I was hoping someone here could guide me through how to start off my Drupal adventure. Setting up a testing environment, which in the end I'll be able to push to a live server and then use it just for coding new features and push them live later.

  • 2
    Welcome to Drupal Answers. Unfortunately, I have to close this. The topic of dev to staging to production is a huge topic that can't be adequately addressed in our question/answer format. It is also an area where Drupal is making progress, but is still lacking. – mpdonadio May 29 '13 at 17:01
  • 1
    Can't believe they won't even allow people to even try to answer this very important question about something that is known to be very difficult in Drupal. Essentially, the standard setup is two (or more) separate Drupal installs, with their own code base and databases, and version control on the code via Git or SVN. The tricky thing then is database migrations (particularly, content migrations) between the sites - solutions to this often involve the module Features; see this q and also this – user56reinstatemonica8 Jun 30 '13 at 16:58
  • actually this question seems to have the best explanation – user56reinstatemonica8 Jun 30 '13 at 17:02

Browse other questions tagged or ask your own question.