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
|
|
@ -8,7 +8,7 @@ tags:
|
|||
- open-source
|
||||
---
|
||||
|
||||
Yesterday's email talked about [writing reusable, framework-agnostic packages](https://www.oliverdavies.uk/archive/2022/10/28/why-write-framework-agnostic-packages) but didn't mention where those packages could be located.
|
||||
Yesterday's email talked about [writing reusable, framework-agnostic packages]({{site.url}}/archive/2022/10/28/why-write-framework-agnostic-packages) but didn't mention where those packages could be located.
|
||||
|
||||
They could be kept within a private repository and still have the same benefits, such as re-usability for internal projects, but I like to open-source code as often as I can and make it available publicly to see and use.
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue