docs(okf): 53 Obsidian wikilinks become OKF links
`[[page|Label]]` is Obsidian syntax, not OKF. `kb-lint` resolves it Obsidian-style — by filename, anywhere in the bundle — so it has never tripped the link gate, while every other consumer of the bundle (an OKF renderer, a Gitea wiki export, `grep` for reachability) sees bracketed text where a link should be. That is how two generated pages ended up with no inbound link at all and nobody noticed: the my-first link census of the bundle reported them as orphans because their only inbound edges were wikilinks. Mechanical conversion, 52 links across 17 pages, each resolved against the same page set `kb-lint` uses: an explicit `|Label` is kept verbatim, an unlabelled link takes the target's frontmatter `title`. Targets are emitted bundle-absolute (`/tools/niri/tips.md`), the form the spec recommends and the form 99 existing links in this bundle already use. Two links were `[[index]]`, which resolves by filename to 21 pages — the ambiguity that filename-resolution invites. Both meant their own directory's index, so both are now written out in full: `/tools/gitea/index.md`, `/tools/niri/index.md`. The linter still tolerates wikilinks; whether it should reject them outright is an open question on #64, because that would replace the two tests pinning today's tolerance. Refs #64
This commit is contained in:
1 parent
4735702965
commit
62a70caebb
17 files changed
+55
-55
No files matched your search
@@ -83,5 +83,5 @@ Note: the full-stack repo compose (`dankclaw/compose.yaml`) maps Gitea HTTP to h
|
||||
## See Also
|
||||
|
||||
- ](index.md) — index with management commands
|
||||
- [[management|management]] — operations, boot persistence, incident
|
||||
- [[data-persistence|data-persistence]] — volumes and backups
|
||||
- [management](/tools/gitea/management.md) — operations, boot persistence, incident
|
||||
- [data-persistence](/tools/gitea/data-persistence.md) — volumes and backups
|
||||
@@ -14,7 +14,7 @@ verified: 2026-10-09
|
||||
Clients (workstations, agent hosts) reach Gitea over plain HTTP on the LAN:
|
||||
`http://192.168.0.143:3000/dank/<repo>.git`. Authentication is a Gitea HTTP token sent as
|
||||
the password for user `dank`. SSH is available on `:2222` (see
|
||||
[[architecture|architecture]]); HTTP + token is what the agent hosts use.
|
||||
[architecture](/tools/gitea/architecture.md)); HTTP + token is what the agent hosts use.
|
||||
|
||||
## The law: the token never enters a URL, a config file, or a shell rc
|
||||
|
||||
@@ -93,6 +93,6 @@ until it is deleted in the UI, so delete it there as part of the rotation.
|
||||
|
||||
## See Also
|
||||
|
||||
- [[index|index]] — Gitea on dankclaw
|
||||
- [[management|management]] — server-side operations
|
||||
- [[architecture|architecture]] — ports (3000 HTTP, 2222 SSH) and the Caddy front
|
||||
- [Gitea directory index](/tools/gitea/index.md) — Gitea on dankclaw
|
||||
- [management](/tools/gitea/management.md) — server-side operations
|
||||
- [architecture](/tools/gitea/architecture.md) — ports (3000 HTTP, 2222 SSH) and the Caddy front
|
||||
@@ -64,5 +64,5 @@ Set `PGPASSWORD` from `/home/dank/Containers/gitea/env` (mode 0600, `GITEA_DB_PA
|
||||
## See Also
|
||||
|
||||
- ](index.md) — index with management commands
|
||||
- [[management|management]] — operations and boot persistence
|
||||
- [[architecture|architecture]] — network and ports
|
||||
- [management](/tools/gitea/management.md) — operations and boot persistence
|
||||
- [architecture](/tools/gitea/architecture.md) — network and ports
|
||||
@@ -39,13 +39,13 @@ All data lives on host bind mounts under `/home/dank/Containers/gitea/` (fleet s
|
||||
| `/home/dank/Containers/gitea/postgres/` | PostgreSQL data files |
|
||||
| `/home/dank/Containers/gitea/env` | EnvironmentFile (mode 0600; `GITEA_DB_PASSWORD`) |
|
||||
|
||||
See [[data-persistence|data-persistence]] for backup and restore.
|
||||
See [data-persistence](/tools/gitea/data-persistence.md) for backup and restore.
|
||||
|
||||
## Boot Persistence
|
||||
|
||||
User-level linger is enabled for `dank`. The units start at host boot without a login. Each unit carries `[Install] WantedBy=default.target`; the podman generator applies it. The legacy podman-compose stack had no units and did not survive reboots (incident 2026-08-16).
|
||||
|
||||
See [[management|management]] for boot persistence details and troubleshooting.
|
||||
See [management](/tools/gitea/management.md) for boot persistence details and troubleshooting.
|
||||
|
||||
## Repo Copies
|
||||
|
||||
|
||||
@@ -100,7 +100,7 @@ Verify the fix on the next host reboot.
|
||||
## See Also
|
||||
|
||||
- ](index.md) — index
|
||||
- [[client-access|client-access]] — how client hosts authenticate (token + credential store)
|
||||
- [[architecture|architecture]] — network topology
|
||||
- [[data-persistence|data-persistence]] — backups
|
||||
- [[containers|containers]] — quadlet reference
|
||||
- [client-access](/tools/gitea/client-access.md) — how client hosts authenticate (token + credential store)
|
||||
- [architecture](/tools/gitea/architecture.md) — network topology
|
||||
- [data-persistence](/tools/gitea/data-persistence.md) — backups
|
||||
- [containers](/engineering/infra/containers.md) — quadlet reference
|
||||
Reference in new issue
Block a user