I can see the answers provided for Drupal 8 here: https://drupal.stackexchange.com/questions/188817/how-to-prevent-devel-m...
Which if any of these methods work with Backdrop CMS? Are there other methods to consider?
I can see the answers provided for Drupal 8 here: https://drupal.stackexchange.com/questions/188817/how-to-prevent-devel-m...
Which if any of these methods work with Backdrop CMS? Are there other methods to consider?
Comments
That's a good question. I don't think there's a method at the moment other than manually enabling/disabling modules. There's no Config Split and the Backdrop drush config export command can only export everything. https://github.com/backdrop-contrib/drush/blob/1.x-0.x/commands/config/b...
You can add an issue there if you wish for the feature.
Something like config split wouldn't help in Backdrop because module status is not stored in configuration, it's in the database. What are the solutions for this in Drupal 7? We should be looking to those to find a comparable solution for Backdrop.
In D7, I played with the Habitat module. If module status is stored in the db though, perhaps I should just handle this in my deployment script..