-2

For D8 do you deploy core and vendor directories to GitHub? Or do you run separately composer update on local and production?

ADV/DIS with core deployment to Git:

+ run composer update once

- time consuming

- ?

PS. I'm using Cloudways.

New contributor
adpo is a new contributor to this site. Take care in asking for clarification, commenting, and answering. Check out our Code of Conduct.
  • Short answer: No. Use a CI service like TravisCI/Circle CI or evening GitLab CI or GitHub Actions (I have not used this one yet) to build, test, and deploy your artifact to the server. – Kevin Jan 14 at 14:31
  • Welcome to Drupal Answers! :-) That's an opinion-based issue. Depends on you. But "normally" you'd keep everything out of the repo that's covered from a package manager. Means no core, no vendor in the repo (core is part of vendor depending on the Composer template you are using). Some then deploy the whole build to their production server and let Drush do the rest, others SSH to production and run composer install -n --no-dev and then Drush. Up to you. – leymannx Jan 14 at 14:32
  • @leymannx Thank you for reply. I'm looking your value option, because even default gitignore file doesn't exclude core folder. I presume people are using both methods ... – adpo Jan 14 at 14:53
  • Well, the example.gitignore says the following: Ignore core when managing all of a project's dependencies with Composer including Drupal core. – leymannx Jan 14 at 14:58
  • 2
    For two years now I have gitignored core/vendor and virtually anything that was not custom modules and custom themes. I wrote about this a little bit ago, it might shed light on it for you kevinquillen.com/deploying-drupal-8 – Kevin Jan 14 at 15:48

Your Answer

adpo is a new contributor. Be nice, and check out our Code of Conduct.

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.