1

I've previously been told that I should not put content on Pantheon in the development environment.

The reason was not explained.

Can anyone think of any reason that this should be advised?

I can see that pulling/pushing a lot of content form the /files directory could be and issue but is there any other reason that anyone can think of?

Thanks,

Andy

  • 2
    Are you sure it was put exactly like that? I'd imagine you've been advised that the proper direction for your DB workflow is Live -> Staging -> Testing, not the other way around. The reason should hopefully be obvious: content is added by users on the live site, and if you then overwrite that db with your dev db, where the new content doesn't exist, you'll wipe it out – Clive Jan 31 '14 at 12:53
  • In all honesty it was said to a colleague and not directly to me. I'm trying to clarify the logic behind the statement. Thanks for your input Clive. – AndA Jan 31 '14 at 12:57
  • 1
    Gotcha...the phrase "I should not put content on Pantheon in the development environment" is definitely incorrect in and of itself, that's why I asked. The person was probably referring to a live environment where multiple users edit content, and who don't have access to the dev server site. In such a case moving the database from Testing -> Staging -> Live would obviously be a big no-no as you'd overwrite changes - so content should go in on live only in that case. It's the same workflow recommended for Drush IIRC – Clive Jan 31 '14 at 13:00
  • Great. I'll go with that as a reason as I'm not entirely confident I can see another. It will not affect us as we will be hosting Live elsewhere. It will therefore just be test content whilst the site is in development. – AndA Jan 31 '14 at 13:02

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.