Use environment-specific URLs instead of
...hard-coded ones
This commit is contained in:
parent
6ca5704c21
commit
1b05e63a20
76 changed files with 91 additions and 91 deletions
|
@ -10,7 +10,7 @@ tags:
|
|||
|
||||
I've been working on a project with a client, using [Fractal](https://fractal.build) 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.
|
||||
|
||||
I recently added `node` support to my [build configuration file generator](https://www.oliverdavies.uk/archive/2023/03/04/why-i-built-a-tool-to-generate-configuration-files) and used that to generate and use a consistent set of configuration files for a Fractal project.
|
||||
I recently added `node` support to my [build configuration file generator]({{site.url}}/archive/2023/03/04/why-i-built-a-tool-to-generate-configuration-files) and used that to generate and use a consistent set of configuration files for a Fractal project.
|
||||
|
||||
I've used Terraform in [some codebases](https://github.com/opdavies/rebuilding-acquia) 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.
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue