81 lines
2.5 KiB
YAML
81 lines
2.5 KiB
YAML
|
uuid:
|
||
|
|
- value: 593bdaf4-b28c-4938-b1da-03052baef361
|
||
|
|
langcode:
|
||
|
|
- value: en
|
||
|
|
type:
|
||
|
|
- target_id: daily_email
|
||
|
|
target_type: node_type
|
||
|
|
target_uuid: 8bde1f2f-eef9-4f2d-ae9c-96921f8193d7
|
||
|
|
revision_timestamp:
|
||
|
|
- value: '2025-05-11T09:00:04+00:00'
|
||
|
|
revision_uid:
|
||
|
|
- target_type: user
|
||
|
|
target_uuid: b8966985-d4b2-42a7-a319-2e94ccfbb849
|
||
|
|
revision_log: { }
|
||
|
|
status:
|
||
|
|
- value: true
|
||
|
|
uid:
|
||
|
|
- target_type: user
|
||
|
|
target_uuid: b8966985-d4b2-42a7-a319-2e94ccfbb849
|
||
|
|
title:
|
||
|
|
- value: 'drush deploy'
|
||
|
|
created:
|
||
|
|
- value: '2024-11-18T00:00:00+00:00'
|
||
|
|
changed:
|
||
|
|
- value: '2025-05-11T09:00:04+00:00'
|
||
|
|
promote:
|
||
|
|
- value: false
|
||
|
|
sticky:
|
||
|
|
- value: false
|
||
|
|
default_langcode:
|
||
|
|
- value: true
|
||
|
|
revision_translation_affected:
|
||
|
|
- value: true
|
||
|
|
path:
|
||
|
|
- alias: /daily/2024/11/18/drush-deploy
|
||
|
|
langcode: en
|
||
|
|
body:
|
||
|
|
- value: |
|
||
|
|
<p>This week I learned about the <a href="https://www.drush.org/13.x/deploycommand">drush deploy command</a>.</p>
|
||
|
|
|
||
|
|
<p>It's been available since Drush 10.3 and combines several commands together in an attempt to "standardise how Drupal deployments work".</p>
|
||
|
|
|
||
|
|
<p>These commands are:</p>
|
||
|
|
|
||
|
|
<pre><code class="shell">drush updatedb
|
||
|
|
drush config:import
|
||
|
|
drush cache:rebuild
|
||
|
|
drush deploy:hook
|
||
|
|
</code></pre>
|
||
|
|
|
||
|
|
<p>Usually, I run these commands separately but grouping them and standardising makes a lot of sense.</p>
|
||
|
|
|
||
|
|
<p><code>drush deploy:hook</code> is also very interesting and allows for adding deploy hooks similar to update hooks in .install files.</p>
|
||
|
|
|
||
|
|
<p>I'm looking forward to updating my deployment pipelines to use this and making them simpler and easier to maintain.</p>
|
||
|
|
|
||
|
|
|
||
|
|
format: full_html
|
||
|
|
processed: |
|
||
|
|
<p>This week I learned about the <a href="https://www.drush.org/13.x/deploycommand">drush deploy command</a>.</p>
|
||
|
|
|
||
|
|
<p>It's been available since Drush 10.3 and combines several commands together in an attempt to "standardise how Drupal deployments work".</p>
|
||
|
|
|
||
|
|
<p>These commands are:</p>
|
||
|
|
|
||
|
|
<pre><code class="shell">drush updatedb
|
||
|
|
drush config:import
|
||
|
|
drush cache:rebuild
|
||
|
|
drush deploy:hook
|
||
|
|
</code></pre>
|
||
|
|
|
||
|
|
<p>Usually, I run these commands separately but grouping them and standardising makes a lot of sense.</p>
|
||
|
|
|
||
|
|
<p><code>drush deploy:hook</code> is also very interesting and allows for adding deploy hooks similar to update hooks in .install files.</p>
|
||
|
|
|
||
|
|
<p>I'm looking forward to updating my deployment pipelines to use this and making them simpler and easier to maintain.</p>
|
||
|
|
|
||
|
|
|
||
|
|
summary: null
|
||
|
|
field_daily_email_cta: { }
|