Move all files to tome/

tome/content/node.d7a77497-05c5-4a42-8ecc-e0f171bb8097.yml

@@ -0,0 +1,96 @@
+uuid:
+  - value: d7a77497-05c5-4a42-8ecc-e0f171bb8097
+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: 'Import or install?'
+created:
+  - value: '2024-12-28T00: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/28/import-install
+    langcode: en
+body:
+  - value: |
+      <p>How do you update your environments?</p>
+
+      <p>I've done it in two different ways on different projects.</p>
+
+      <p>The most common way is to download a database from another environment and import it.</p>
+
+      <p>The downside is that there needs to be a blessed database for everyone to use and someone needs to maintain and update.</p>
+
+      <p>It can also contain user data, such as usernames, email addresses, passwords and webform submissions that you should sanitise or remove.</p>
+
+      <p>The other option is to install the application from scratch.</p>
+
+      <p>For Drupal projects, this means installing using the existing configuration to re-create the content types, fields, views, block types, etc.</p>
+
+      <p>This confirms the configuration is installable or it will fail.</p>
+
+      <p>As it's a fresh installation, it can be run by anyone without needing to maintain an blessed database and doesn't contain any user data.</p>
+
+      <p>Then you can recreate any data, such as users or content, that you need or seed the database with standard data.</p>
+
+      <p>For Drupal, <a href="/daily/2024/09/16/experimenting-with-the-default-content-module">I've been using the Default Content module</a> for this, which has been working very well.</p>
+
+      <p>If I can, I much prefer the install approach rather than importing.</p>
+
+      <p>Which do you do, or do you do something else?</p>
+
+              
+    format: full_html
+    processed: |
+      <p>How do you update your environments?</p>
+
+      <p>I've done it in two different ways on different projects.</p>
+
+      <p>The most common way is to download a database from another environment and import it.</p>
+
+      <p>The downside is that there needs to be a blessed database for everyone to use and someone needs to maintain and update.</p>
+
+      <p>It can also contain user data, such as usernames, email addresses, passwords and webform submissions that you should sanitise or remove.</p>
+
+      <p>The other option is to install the application from scratch.</p>
+
+      <p>For Drupal projects, this means installing using the existing configuration to re-create the content types, fields, views, block types, etc.</p>
+
+      <p>This confirms the configuration is installable or it will fail.</p>
+
+      <p>As it's a fresh installation, it can be run by anyone without needing to maintain an blessed database and doesn't contain any user data.</p>
+
+      <p>Then you can recreate any data, such as users or content, that you need or seed the database with standard data.</p>
+
+      <p>For Drupal, <a href="/daily/2024/09/16/experimenting-with-the-default-content-module">I've been using the Default Content module</a> for this, which has been working very well.</p>
+
+      <p>If I can, I much prefer the install approach rather than importing.</p>
+
+      <p>Which do you do, or do you do something else?</p>
+
+              
+    summary: null
+field_daily_email_cta: {  }