![]() Do you really need a distribution? Can you do the work with composer instead, which could be a more modern approach for some solutions?Įnsuring you know all possibilities, pros and cons should help you making that decision: ![]() ![]() Regarding distributions on itself, as everything in life, it all depends. The distro is free to use, but if you are not using those products, and given that current approach of product integration, you probably don't need ACMS. If you are a customer of those, Acquia CMS (like any other distro) should increase your initial build and time to market, when building a new site or platform. None of that makes much sense when Composer is available.Īcquia CMS comes integrated with a few of the Acquia products, like Search or Site Studio. as was the decision to leverage Drush Make to package the install profile with its dependencies in a single, compressed download. What we did to add support for non-core install profiles 10+ years ago was largely based on extending how modules worked. The shift from packaged installs that do everything from manage the code being downloaded, installing Drupal and managing updates to a more modern, project template approach being discussed in is really interesting. I personally had high hopes for the Install Profile Inheritance approach that Lightning used, but after 10+ years of that approach and contributions for the developers working on most of the popular Drupal profiles, it's clear that is not a great approach either. While this seemed like a good idea at the time, it proved to be really difficult to maintain. This worked relatively well because the install profiles were designed to be switched by only building on the previous install. ![]() Profile Switcher was originally developed to allow Community Media groups to move to increasingly complicated D7 configurations Easy -> Moderate -> Difficult. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |