novox/mesh-controller
3
0
Fork 0
Code Issues Pull Requests 1 Releases Wiki Activity

Reference the record rather than link across repositories

Browse Source 
A relative link out of this repository resolves nowhere on a forge. Every
other reference here names the record in prose.
This commit is contained in:
jschoubben
2026-08-31 17:52:25 +02:00
parent 950ebb9e28
commit 981cd4139b
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
examples/modules/README.md
+1 -1
View File
@@ -57,7 +57,7 @@ edge, and they are here as a **pair** because that is the only way to see the ha
the private network. Neither manifest names an address, and that is what lets the same pair work
on any mesh.
**`s3-bucket` names the protocol, not the product** ([ADR 0027](../../../hq/02-DECISIONS/)). A
**`s3-bucket` names the protocol, not the product** (novox/hq ADR 0027). A
consumer's code is written against the S3 API, and swapping one store for another does not break
it — so the coupling is to S3. A database is the other case: an application is written against
PostgreSQL or against SQL Server, so those provisions name the engine.