![]() ![]() its functionality to generate boilerplate code: it takes no more than a few simple commands to create your custom entity type or custom module.The “new(er) kid on the block”, Drupal Console, comes to question the “Drush supremacy” as the go-to CLI for Drupal developers. ![]() Part of a PHP library, you can install it using Composer. they both boost your productivity as a Drupal developer by streamlining some otherwise time-consuming Drupal development and management tasksĪn only child in the Drupal ecosystem, Drush used to be the go-to command line for speeding up common tasks like:.they're both extensible you get to write your custom commands and to adapt the configuration files to your Drupal project's specific needs.they're both command-line tools that help you get a new Drupal website up and running in no time and keep interacting with your Drupal installation.Drupal Console vs Drush: What Do They Have in Common?īefore we dig out the differences - or better said “different ways of handling the same tasks“ - let's outline some of the obvious similarities between these tools: On one hand, you have good old Drush, with its familiar commands speeding up the most common Drupal development tasks.Īnd on the other hand, you have Drupal Console and the temptation of a newer CLI tool, along with its main strength: to generate the initial scaffolding for a new project.ġ. Those that would eventually help you choose the best CLI for you? When would you choose one over the other? And what would you base your choice on? What are their most powerful commands? In other words: do these 2 command-line tools (still) compliment each other? Can you run them together? And, if not, which one of them should you favor in a Drupal Console vs Drush "debate”?
0 Comments
Leave a Reply. |