From 32009df41dccbc9a70b865002310759922fb70fb Mon Sep 17 00:00:00 2001 From: Oliver Davies Date: Thu, 21 Nov 2024 23:57:44 +0000 Subject: [PATCH] Add daily email for 2024-11-18 drush deploy --- source/_daily_emails/2024-11-18.md | 34 ++++++++++++++++++++++++++++++ 1 file changed, 34 insertions(+) create mode 100644 source/_daily_emails/2024-11-18.md diff --git a/source/_daily_emails/2024-11-18.md b/source/_daily_emails/2024-11-18.md new file mode 100644 index 000000000..91ea917fe --- /dev/null +++ b/source/_daily_emails/2024-11-18.md @@ -0,0 +1,34 @@ +--- +title: drush deploy +date: 2024-11-18 +permalink: daily/2024/11/18/drush-deploy +tags: + - software-development + - drupal + - drush + - php +cta: ~ +snippet: | + Do you use the "drush deploy" command? I found out about it this week and will be refactoring some deployment pipelines to use it. +--- + +This week I learned about the [drush deploy command][0]. + +It's been available since Drush 10.3 and combines several commands together in an attempt to "standardise how Drupal deployments work". + +These commands are: + +```shell +drush updatedb +drush config:import +drush cache:rebuild +drush deploy:hook +``` + +Usually, I run these commands separately but grouping them and standardising makes a lot of sense. + +`drush deploy:hook` is also very interesting and allows for adding deploy hooks similar to update hooks in .install files. + +I'm looking forward to updating my deployment pipelines to use this and making them simpler and easier to maintain. + +[0]: https://www.drush.org/13.x/deploycommand