Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[META] CMI conversions #169

Closed
28 tasks done
jenlampton opened this issue Feb 7, 2014 · 4 comments
Closed
28 tasks done

[META] CMI conversions #169

jenlampton opened this issue Feb 7, 2014 · 4 comments

Comments

@jenlampton
Copy link
Member

The basic idea of configuration management is that functionality assembled on a development environment should be able to be deployed on a different (staging or production) environment. The configuration should be stored in version-controlled files and stored with code, rather than being mixed with content in the database.

This issue contains the complete list of all conversions to configuration management.

STATES

VARIABLES

SYSTEMS

POSTPONED CONVERSIONS (for now)

CMI D8 Issues for review (oldest to newest)

For reference, here is the meta issue from drupal.org

@jenlampton
Copy link
Member Author

@quicksketch I just added all the CMI issues we had so far from the D8 backports here for your review.

@docwilmot
Copy link
Contributor

Just to be clear, there is still a boat-load of variable_get() calls in the latest bd; are these all going away? Should someone make a list then?

@quicksketch
Copy link
Member

Hi @docwilmot! Yes, we're working to remove all variables, except where we're retrieving them in .install files as part of the upgrade path. I have a PR to convert most of the remaining variables in #170, except language variables, which is a larger and separate task that we should do in #175.

@quicksketch
Copy link
Member

Our last item here was text formats in #172. Now with it complete, we have everything we intend to include in configuration for the first release, with upgrade paths from Drupal 7. w00t!

There are number of limitations that we accepted in our config system, so I've made a new meta for CMI in Backdrop 2.x that includes the main features in config management on which we had to compromise.

I'm thrilled with the functionality we'll deliver in our 1.0 release. Even though we haven't solved every possible configuration problem, we're still light years ahead of Drupal 7 + Features module.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants