Use environment-specific URLs instead of

...hard-coded ones
This commit is contained in:
Oliver Davies 2024-09-03 00:34:58 +01:00
parent 6ca5704c21
commit 1b05e63a20
76 changed files with 91 additions and 91 deletions

View file

@ -10,7 +10,7 @@ I'm always working on various personal and client projects, and they contain a l
The majority of those files are the same with some slight configuration for each project - such as whether it uses `web` or `docroot`, or which paths are checked with static analysis or for coding standards issues.
I've given a talk called [Working with Workspace](https://www.oliverdavies.uk/presentations/working-with-workspace) - a tool that we used at an agency I worked at. It had two functions - to execute project tasks and to generate configuration files from templates.
I've given a talk called [Working with Workspace]({{site.url}}/presentations/working-with-workspace) - a tool that we used at an agency I worked at. It had two functions - to execute project tasks and to generate configuration files from templates.
I use a `justfile` to execute tasks and commands but needed to write my own tool to generate the configuration files.