0

I want to deploy my drupal project to higher environment - DEV -> QA --> Staging --> Production. So i understand the following moving parts

1) Drupal code - everything inside var/www/html. (this is automated using Jenkins once we check the code in GIT.) 2) Database (manual) 3) File system - we are using S3. (Manual).

I would like to do incremental push to higher environments - i do not want to dump the complete DB for every release.

If clients add few modules in Staging environment or do some setting changes in staging and production environment, how to retain the information when i do a next release? Please help.

4
  • Are you working on Drupal 8 project? or Drupal 7? Mar 21 '18 at 13:24
  • I suggest never allowing the addition of modules in the server environment. The best way is adding them with Composer and committing that, then letting a CI server like Travis or Circle build the artifact and push it to the correct environment.
    – Kevin
    Mar 21 '18 at 14:16
  • it is drupal 8.4 Mar 27 '18 at 18:45
  • Kevin - thanks. It looks like the best option. How are dealing with files (PDFs , Docs etc). Currently we have files in S3. So first time i am good with syncing DB and files as a whole. But how about later releases. Is there an option to do incremental or delta pushes. Mar 27 '18 at 18:47

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.