opdavies/oliverdavies.uk
1
0
Fork 0
Code Issues 1 Pull requests Projects 1 Releases Packages Wiki Activity Actions

Make all links relative

Browse source 
Now the abs_to_rel module is enabled, links can be made relative so they
work on the current environment.
This commit is contained in:
Oliver Davies 2025-05-29 16:42:25 +01:00
parent 0d359f81d6
commit 7a7dc297ca
349 changed files with 698 additions and 698 deletions
Download patch file Download diff file Expand all files Collapse all files

4
content/node.8f2bed8f-56cb-4269-8e1d-082af6201775.json
View file

@ -82,9 +82,9 @@
],
"body": [
{
"value": "\n <p>I'm always working on various personal and client projects, and they contain a lot of the same configuration files. I exclusively use Docker and Docker Compose on all projects, I use a <code>justfile<\/code> for running tasks, and for PHP projects, I need configuration files for tools like PHPStan, PHPCS and PHPUnit.<\/p>\n\n<p>The majority of those files are the same with some slight configuration for each project - such as whether it uses <code>web<\/code> or <code>docroot<\/code>, or which paths are checked with static analysis or for coding standards issues.<\/p>\n\n<p>I've given a talk called <a href=\"https:\/\/www.oliverdavies.uk\/presentations\/working-with-workspace\">Working with Workspace<\/a> - 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.<\/p>\n\n<p>I use a <code>justfile<\/code> to execute tasks and commands but needed to write my own tool to generate the configuration files.<\/p>\n\n<p>The result is that I can add one YAML file to a project, enter the values that it needs and when I run the CLI tool, it will generate all of the files the project needs.<\/p>\n\n<p>As well as being faster to set up a project, like a <a href=\"https:\/\/github.com\/opdavies\/docker-examples\/tree\/main\/drupal-localgov\">LocalGov Drupal Docker example<\/a>, having a canonical set of templated configuration files I can enhance and maintain by adding new features and fixes and they'll be added to every project when I next generate its files.<\/p>\n\n ",
"value": "\n <p>I'm always working on various personal and client projects, and they contain a lot of the same configuration files. I exclusively use Docker and Docker Compose on all projects, I use a <code>justfile<\/code> for running tasks, and for PHP projects, I need configuration files for tools like PHPStan, PHPCS and PHPUnit.<\/p>\n\n<p>The majority of those files are the same with some slight configuration for each project - such as whether it uses <code>web<\/code> or <code>docroot<\/code>, or which paths are checked with static analysis or for coding standards issues.<\/p>\n\n<p>I've given a talk called <a href=\"/presentations\/working-with-workspace\">Working with Workspace<\/a> - 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.<\/p>\n\n<p>I use a <code>justfile<\/code> to execute tasks and commands but needed to write my own tool to generate the configuration files.<\/p>\n\n<p>The result is that I can add one YAML file to a project, enter the values that it needs and when I run the CLI tool, it will generate all of the files the project needs.<\/p>\n\n<p>As well as being faster to set up a project, like a <a href=\"https:\/\/github.com\/opdavies\/docker-examples\/tree\/main\/drupal-localgov\">LocalGov Drupal Docker example<\/a>, having a canonical set of templated configuration files I can enhance and maintain by adding new features and fixes and they'll be added to every project when I next generate its files.<\/p>\n\n ",
"format": "full_html",
"processed": "\n <p>I'm always working on various personal and client projects, and they contain a lot of the same configuration files. I exclusively use Docker and Docker Compose on all projects, I use a <code>justfile<\/code> for running tasks, and for PHP projects, I need configuration files for tools like PHPStan, PHPCS and PHPUnit.<\/p>\n\n<p>The majority of those files are the same with some slight configuration for each project - such as whether it uses <code>web<\/code> or <code>docroot<\/code>, or which paths are checked with static analysis or for coding standards issues.<\/p>\n\n<p>I've given a talk called <a href=\"https:\/\/www.oliverdavies.uk\/presentations\/working-with-workspace\">Working with Workspace<\/a> - 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.<\/p>\n\n<p>I use a <code>justfile<\/code> to execute tasks and commands but needed to write my own tool to generate the configuration files.<\/p>\n\n<p>The result is that I can add one YAML file to a project, enter the values that it needs and when I run the CLI tool, it will generate all of the files the project needs.<\/p>\n\n<p>As well as being faster to set up a project, like a <a href=\"https:\/\/github.com\/opdavies\/docker-examples\/tree\/main\/drupal-localgov\">LocalGov Drupal Docker example<\/a>, having a canonical set of templated configuration files I can enhance and maintain by adding new features and fixes and they'll be added to every project when I next generate its files.<\/p>\n\n ",
"processed": "\n <p>I'm always working on various personal and client projects, and they contain a lot of the same configuration files. I exclusively use Docker and Docker Compose on all projects, I use a <code>justfile<\/code> for running tasks, and for PHP projects, I need configuration files for tools like PHPStan, PHPCS and PHPUnit.<\/p>\n\n<p>The majority of those files are the same with some slight configuration for each project - such as whether it uses <code>web<\/code> or <code>docroot<\/code>, or which paths are checked with static analysis or for coding standards issues.<\/p>\n\n<p>I've given a talk called <a href=\"/presentations\/working-with-workspace\">Working with Workspace<\/a> - 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.<\/p>\n\n<p>I use a <code>justfile<\/code> to execute tasks and commands but needed to write my own tool to generate the configuration files.<\/p>\n\n<p>The result is that I can add one YAML file to a project, enter the values that it needs and when I run the CLI tool, it will generate all of the files the project needs.<\/p>\n\n<p>As well as being faster to set up a project, like a <a href=\"https:\/\/github.com\/opdavies\/docker-examples\/tree\/main\/drupal-localgov\">LocalGov Drupal Docker example<\/a>, having a canonical set of templated configuration files I can enhance and maintain by adding new features and fixes and they'll be added to every project when I next generate its files.<\/p>\n\n ",
"summary": null
}
],