65 lines
3.6 KiB
YAML
65 lines
3.6 KiB
YAML
uuid:
|
|
- value: 7b840e91-b45a-4403-8b34-6b9b4dda2ebf
|
|
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:46+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: |
|
|
The benefits of automation
|
|
created:
|
|
- value: '2023-03-15T00:00:00+00:00'
|
|
changed:
|
|
- value: '2025-05-11T09:00:46+00:00'
|
|
promote:
|
|
- value: false
|
|
sticky:
|
|
- value: false
|
|
default_langcode:
|
|
- value: true
|
|
revision_translation_affected:
|
|
- value: true
|
|
path:
|
|
- alias: /daily/2023/03/15/the-benefits-of-automation
|
|
langcode: en
|
|
body:
|
|
- value: |
|
|
<p>I've been working on a project with a client, using <a href="https://fractal.build">Fractal</a> for our component library. I've been working on it locally but yesterday I needed to make it public for the client to review the work I've done.</p>
|
|
|
|
<p>I recently added <code>node</code> support to my <a href="/daily/2023/03/04/why-i-built-a-tool-to-generate-configuration-files">build configuration file generator</a> and used that to generate and use a consistent set of configuration files for a Fractal project.</p>
|
|
|
|
<p>I've used Terraform in <a href="https://github.com/opdavies/rebuilding-acquia">some codebases</a> to create and configure AWS resources like S3 buckets and Cloudfront distributions, so I was able to use that to create what I needed as well as adding the DNS record for a new subdomain to access Cloudfront.</p>
|
|
|
|
<p>I use a <code>justfile</code> to automate tasks such as generating production assets from Fractal and uploading it to the S3 bucket, so I can do this in a single command instead of multiple and in a consistent and reproducible way.</p>
|
|
|
|
<p>I started with a standalone project on my laptop and finished with a consistent cloud-based environment for my client and their project to review their component library, and because of the automation that I've built and used, this only took a few minutes to do.</p>
|
|
|
|
|
|
format: full_html
|
|
processed: |
|
|
<p>I've been working on a project with a client, using <a href="https://fractal.build">Fractal</a> for our component library. I've been working on it locally but yesterday I needed to make it public for the client to review the work I've done.</p>
|
|
|
|
<p>I recently added <code>node</code> support to my <a href="/daily/2023/03/04/why-i-built-a-tool-to-generate-configuration-files">build configuration file generator</a> and used that to generate and use a consistent set of configuration files for a Fractal project.</p>
|
|
|
|
<p>I've used Terraform in <a href="https://github.com/opdavies/rebuilding-acquia">some codebases</a> to create and configure AWS resources like S3 buckets and Cloudfront distributions, so I was able to use that to create what I needed as well as adding the DNS record for a new subdomain to access Cloudfront.</p>
|
|
|
|
<p>I use a <code>justfile</code> to automate tasks such as generating production assets from Fractal and uploading it to the S3 bucket, so I can do this in a single command instead of multiple and in a consistent and reproducible way.</p>
|
|
|
|
<p>I started with a standalone project on my laptop and finished with a consistent cloud-based environment for my client and their project to review their component library, and because of the automation that I've built and used, this only took a few minutes to do.</p>
|
|
|
|
|
|
summary: null
|
|
field_daily_email_cta: { }
|