Timeline for Composer is git cloning modules instead of download them?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 12, 2018 at 14:41 | comment | added | Kevin | Just as an update - this problem is non-existent if you don't use the tarball from drupal.org and use a composer managed installation. There is also composerize-drupal too. It is beneficial to just sit down and create a deployment workflow around composer instead of commit all. | |
| Oct 28, 2016 at 15:04 | vote | accept | Kevin | ||
| Oct 28, 2016 at 15:04 | comment | added | Kevin | Ok, I just saw composer-patches. Now it is starting to make more sense, in regards to maintaining patches and changes. | |
| Oct 28, 2016 at 14:04 | comment | added | Kevin | Its tough because core update instructions say to replace the vendor folder and run composer update. If you don't use composer to install modules, then you will obliterate their composer deps, Search API with Solarium, for example. | |
| Oct 27, 2016 at 20:40 | history | answered | Berdir | CC BY-SA 3.0 |