Configuration Management Ecosystem

Transcript

7. Configuration Management Ecosystem
8. Configuration Management in a nutshell — CMI was the first Drupal 8 initiative to be announced in 2011 — Store data that needs synchronising in the configuration system
9. Configuration vs. Content vs. Deployment Content: Node, User, Taxonomy Terms, File ... Config: Fields, Content-Types, Form/View Modes, Views, Image Styles ... Standard Profile (8.4.x) 11 Content Entity Types 29 Config Entity Types
10. Holy Grail DEV: drush cex STAGE / PROD: drush updb && drush cim
11. Anwendungsfälle ohne klare Trennung — def. Set an Taxonomy Terms — Default Images (Image Fields etc.) — TAC — Webform — Blocks — Panels
12. Advanced Workflows — Install a site from existing configuration — Environment specific overrides (dev Modules, API credentials)
13. 1. Bootstrap a new site — Config Installer — Install Profile Generator + Core Patch — Drush (+ Custom Profile)
14. 2. Environment specific overrides Overrides in $config (settings.local.php) $config['system.logging']['error_level'] = 'verbose'; $config['system.site']['mail'] = 'foo@example.com'; Limitations — Complex Config with State (e.g. Fields), Module — Not visible in UI, leads to confusion
15. 3. Environment specific overrides Config Split — Multiple Splits — Backlist and Greylist (Stash)
16. Demo :)
17. Was ist mit Features? Features ist für Packaging & Reuse. Nicht Deployment.
18. Contrib Modules — Config Split — Config Installer — Config Override — Configuration Read-only mode — Install Profile Generator
19. Danke! @webflo / @ueberbit