oliverdavies.uk/content/node.0100be71-79ef-44ea-922e-e75fcc26ae16.yml

uuid:
  - value: 0100be71-79ef-44ea-922e-e75fcc26ae16
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:03+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: 'How quickly can you create or update an environment?'
created:
  - value: '2024-12-27T00:00:00+00:00'
changed:
  - value: '2025-05-11T09:00:03+00:00'
promote:
  - value: false
sticky:
  - value: false
default_langcode:
  - value: true
revision_translation_affected:
  - value: true
path:
  - alias: /daily/2024/12/27/quick
    langcode: en
body:
  - value: |
      <p>A common reason why environments aren't updated and get out of sync is because it's a time-consuming or complex task.</p>

      <p>The process should be simple to run, quick, reliable and reproducible.</p>

      <p>It's the same as deploying a change to a staging or production environment.</p>

      <p>You want the same result on every time on every environment.</p>

      <p>You want every environment - including <a href="/daily/2024/12/25/localhost">local development environments</a> to be as consistent as possible to minimise bugs and errors.</p>

      <p>To do this, I automate things to make them as simple as possible.</p>

      <p>I use <a href="/daily/2022/08/15/using-run-file-simplify-project-tasks">run files</a> with commands to import databases, perform updates and run pre-update and post-update tasks.</p>

      <p>I use tools like Nix and <a href="/daily/2024/11/11/could-nix-and-devenv-replace-docker-compose">devenv</a> to create identical and reproducible environments.</p>

      <p>The simpler and quicker is it, the more it can and will be done.</p>

      <p>You can also use automation to perform long or complex tasks outside of working hours such as sanitising and importing large databases.</p>

      <p>The more you can automate, the better.</p>

              
    format: full_html
    processed: |
      <p>A common reason why environments aren't updated and get out of sync is because it's a time-consuming or complex task.</p>

      <p>The process should be simple to run, quick, reliable and reproducible.</p>

      <p>It's the same as deploying a change to a staging or production environment.</p>

      <p>You want the same result on every time on every environment.</p>

      <p>You want every environment - including <a href="/daily/2024/12/25/localhost">local development environments</a> to be as consistent as possible to minimise bugs and errors.</p>

      <p>To do this, I automate things to make them as simple as possible.</p>

      <p>I use <a href="/daily/2022/08/15/using-run-file-simplify-project-tasks">run files</a> with commands to import databases, perform updates and run pre-update and post-update tasks.</p>

      <p>I use tools like Nix and <a href="/daily/2024/11/11/could-nix-and-devenv-replace-docker-compose">devenv</a> to create identical and reproducible environments.</p>

      <p>The simpler and quicker is it, the more it can and will be done.</p>

      <p>You can also use automation to perform long or complex tasks outside of working hours such as sanitising and importing large databases.</p>

      <p>The more you can automate, the better.</p>

              
    summary: null
field_daily_email_cta: {  }