Timeline for Distribute configuration to several sites
Current License: CC BY-SA 3.0
10 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
May 29, 2015 at 4:07 | vote | accept | Chris | ||
May 29, 2015 at 1:31 | answer | added | Chris | timeline score: 0 | |
May 26, 2015 at 9:52 | comment | added | anavarre | Maybe drush config-merge is what you're after: github.com/drush-ops/drush/blob/master/docs/cm.md | |
Apr 23, 2015 at 6:10 | comment | added | user21641 | Cofiguration supports dependencies. Features is more like a comparison tool. You cna import a feature(a set of configuration objects) and then you can see if the configuration on the site is the same as the one that was imported with the feature and if not you can recreate the feature to reflect the actual state or you can revert the site's configuration into feature's state. Currently I'm not sure what are the good cases to use Features in D8 but it's too soon so I'm sure some scenarios will pop up with time. | |
Apr 22, 2015 at 2:42 | comment | added | Chris | I see, thanks. So for packages and own functionality, I'd still need to use Features? The news-section, the gallery-section? Since configuration can't handle dependencies, right? I reckon it'd be possible to write it by hand - but Features seem to be way more efficient. | |
Apr 21, 2015 at 18:47 | comment | added | user21641 | common config would be a configuration entity, ie. a block, a view, a field(storage or instance), a system setting, content type, content type display,...the stuff that is in module's config directory. State on the other hand is site-specific, ie. D7 variables. | |
Apr 20, 2015 at 23:38 | comment | added | Chris | A common config would be what? Something like Content Types/Required Modules/Permissions. And state for the site itself for language, theme_settings etc. How would I create and develop something like a news section with all it's views, blocks and the content type? How about a gallery? | |
Apr 19, 2015 at 7:59 | comment | added | user21641 | Use configuration files for common config and use state for site-specific configuration. | |
Apr 19, 2015 at 5:55 | history | edited | avpaderno♦ | CC BY-SA 3.0 |
removed thanks and signature
|
Apr 19, 2015 at 0:20 | history | asked | Chris | CC BY-SA 3.0 |