CLI in Core Initiative Update #1

Last week we kicked off the initiative with a synchronous meeting using video chat followed up by creating Slack threads to continue the conversation for the week. This time was set to be friendly for Americas and Europe/Africa to start with based on discussions at DrupalCon Chicago 2026, but we talked about the best strategy to continue meetings at different times.

Before the meeting, I swapped into developer mode and fixed the test failures in package_manager after a lot of debugging to figure out how it was creating directories and running composer. That’s right, we’re green!

My initial...

https://nokoto.org/user/3/posts/905

CLI in Core Initiative Update #1

nokoto

It’s not small core nor big core. (No, it’s not)

It’s not Canvas in core nor the marketplace. (No, it’s not)

It’s clean core 🫧✨

 

... No, I haven’t been drinking.

Preventing a `drush updb` from clearing your caches. #drupal #drush
https://mglaman.dev/blog/preventing-drush-updb-clearing-your-caches
Preventing a `drush updb` from clearing your caches

By default, drush updb clears the cache after applying database updates. For deployments where you want to avoid an unnecessary performance hit, you can prevent this default behavior using a Drush pre-command hook. The updb command has a --cache-clear flag that you can set up in your CI workflow, but what about local testing? Will you or your team remember to set that flag every time?

mglaman.dev
Preventing a `drush updb` from clearing your caches

By default, drush updb clears the cache after applying database updates. For deployments where you want to avoid an unnecessary performance hit, you can prevent this default behavior using a Drush pre-command hook. The updb command has a --cache-clear flag that you can set up in your CI workflow, but what about local testing? Will you or your team remember to set that flag every time?

mglaman.dev
Preventing a `drush updb` from clearing your caches

By default, drush updb clears the cache after applying database updates. For deployments where you want to avoid an unnecessary performance hit, you can prevent this default behavior using a Drush pre-command hook. The updb command has a --cache-clear flag that you can set up in your CI workflow, but what about local testing? Will you or your team remember to set that flag every time?

mglaman.dev
Afficher une barre de progression (progress bar) dans une commande drush

Voici comment afficher une barre de progression (progress bar) dans une commande drush Mon fichier de commande drush ./web/modules/mon_module/src/Drush/Commands/MonModuleCommands.php

Kgaut.NET - Kevin Gautreau
New release of #Drupal Entity Share (https://www.drupal.org/project/entity_share) adds a #Drush command to pull specific entities. Now I need to work out how to make a deployment workflow with #Robo.
Entity Share

Entity Share is a collection of modules allowing you to share content entities like nodes, taxonomy terms, medias etc. between different Drupal instances.

Drupal.org

Check out the latest updates to Drupal at Your Fingertips, a free quick-reference for Drupal developers: https://www.drupalatyourfingertips.com

Please share with colleagues, contribute your code snippets or lessons learned, or support the effort via GitHub Sponsors: https://github.com/sponsors/selwynpolit

#Drupal #PHP #Development #Drush #DDEV #DrupalBook

drush generate module walk-through

The best place to start when familiarising yourself with "drush generate..." commands is "drush generate module" because this provides the module framework onto which other generate commands can build files, e.g. "drush generate plugin:manager". This is often a dev's first experience of "drush generate..." and first impressions are important!

jofitz
drush generate module walk-through

The best place to start when familiarising yourself with "drush generate..." commands is "drush generate module" because this provides the module framework onto which other generate commands can build files, e.g. "drush generate plugin:manager". This is often a dev's first experience of "drush generate..." and first impressions are important!

jofitz