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:
|
|||
- docker
|
||||
---
|
||||
|
||||
A side effect of [using a tool to generate build configuration files](https://www.oliverdavies.uk/archive/2023/03/04/why-i-built-a-tool-to-generate-configuration-files) with templates is the consistency that it introduces.
|
||||
A side effect of [using a tool to generate build configuration files]({{site.url}}/archive/2023/03/04/why-i-built-a-tool-to-generate-configuration-files) with templates is the consistency that it introduces.
|
||||
|
||||
The majority of my projects use a PHP-FPM or PHP CLI container. In my Docker Compose file, the service was mostly named `php` but sometimes it was `php-fpm`. In the templated file, it's always named `php`.
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue