3 ms·
Configuration management is an enormous pain for systems like Drupal that are essentially built ad-hoc, though. It's not something that's practically baked into
by eropple 12y ago
Configuration management is an enormous pain for systems like Drupal that are essentially built ad-hoc, though. It's not something that's practically baked into something like Chef unless you're willing to spend a ton--a ton--of time baking your assumptions into code. And that (along with stuff like a test infrastructure) assume the capability of even doing it; Bob's Bait Shop does not have the technical staff necessary to act according to best practices but definitely needs a website. ("Use SquareSpace" is rarely an answer, though depending on the project it can be; anything remotely clever is going to need to go outside of the usual SaaS providers and that's why there are so many rickety Drupal sites out there. I used to write them, I know.)
Once again, software is harder than it needs to be. Gary Bernhardt has been going into this in depth on Twitter lately, and I agree with him more and more as I pay more attention to the shitshow around us.
- noir_lord 12y ago> Configuration management is an enormous pain for systems like Drupal As someone who worked on Drupal for a couple of year in the days of 5/6 this was my biggest problem. I don't think things have improved much.
- geerlingguy 12y agoThings have improved greatly! With Drupal 7, there are two main solutions, the configuration management module, and features. With Drupal 8 (likely coming out within the next year, currently in beta) YAML-based exportable configuration management is baked into core and will be much more accessible for custom development and contributed modules.
- eropple 12y agoSure. Now they need to grapple with the fundamental differences between install-and-tweak and design-through-code to actually make this meaningful in a modern (Chef/Puppet/Docker) environment. I won't be holding my breath.
- geerlingguy 12y agoA modern, well-architected site build works wonderfully with the aforementioned tools. In fact, I have a demonstration VM (Vagrant + Ansible) that you can use to bootstrap a Drupal site with a given install profile/configuration in a few minutes using a Drush makefile: https://github.com/geerlingguy/drupal-dev-vm https://github.com/geerlingguy/drupal-dev-vm Sadly, most Drupal developers and development shops either don't know about or don't care to take the time to build sites in this manner (instead of schlepping databases and file dumps all over the place, export everything to code)... but if you do, team-based/large project Drupal development becomes so much more sane.
- eropple 12y agoI'm aware of drush and its makefiles. In the overwhelming case, that's antithetical to how working on Drupal actually is, because of the amount of exploration and tweaking involved. It's not a sufficiently simple product such that you can just eyeball a makefile and go.
- pessimizer 12y agoDrupal, in particular, is harder than it has to be. I really liked this article from Sam Boyer: https://medium.com/@sdboyer/keeping-it-simple-944526c5b7fb https://medium.com/@sdboyer/keeping-it-simple-944526c5b7fb