| A | B | C | D | E | F | |
|---|---|---|---|---|---|---|
1 | Drush Make + Profile Make | Platform Git repo | Multisite Git repo | |||
2 | Git repo | Per Project on make file | Per project on root folder with submodules | Per project on sites/example.com folder | ||
3 | New technology | Drush make (nice but no profit) Profiles | Platform git clone with Aegir/Jenkins | Multisite | ||
4 | Local dev | Clone Repo and run drush make | Clone repo | Clone make and run drush make then clone site repo | ||
5 | Pros | Fully automated Small repo Patches/Non git projects Most common way (mig5) Advanced tasks | Fully automated Per project codebase Maintained and deployed with git and drush | Easy and clean deployment with hosting_site_git Deploy git tags Easy updates of core and contrib modules | ||
6 | Cons | Updates difficult Big overhead for small projects Git tag deployment functionality missing | Updates difficult Git tag deployment functionality missing | Maintainability with dursh | ||
7 | ||||||
8 | ||||||
9 | ||||||
10 | ||||||
11 | ||||||
12 | ||||||
13 | ||||||
14 | ||||||
15 | ||||||
16 | ||||||
17 | ||||||
18 | ||||||
19 | ||||||
20 |