Bind org wikis from identically-named -wiki folders #55

Merged

parkerhdavis merged 1 commit from obsidian-vault-folder-labels into main

2026-10-15 22:57:46 -06:00

parkerhdavis commented

2026-10-15 22:57:40 -06:00

(Migrated from github.com)

What happened

The org wikis moved from ~/<Org>/<Org>-Wiki to ~/<Org>/-wiki on every phd-* host, so all eight org wikis now share one literal folder name. The folder name can no longer identify a vault, and the old wiring used it for everything: the host bind source, the container mount target, the remote vault label, and ob's per-vault state key.

What changed

The compose bind sources now point at the new folders (${OBSIDIAN_VAULTS_BASE}/{Org}/-wiki).
The bind targets and OBSIDIAN_VAULT_NAME keep the unique vault labels (Anthers-Wiki, Software-Wiki, …), which continue to name the remote vault and key ob's per-vault setup state in the shared obsidian-headless-state volume. Recreated containers find their existing remotes by label and skip setup as before — no re-link churn, no state reset.
Cross-host safety: a remote labeled exactly with the bare -wiki folder name would have cross-linked each vault's folder to the first container's remote; labels avoid that.
Removed the leftover ${OBSIDIAN_VAULTS_BASE}/PhD-Wiki:/vaults/PhD-Wiki mount dangling under obsidian-filmmaking-wiki in all three compose files (the vault was dissolved 2026-10-12 and the entrypoint never synced it — but Docker did auto-create its root-owned bind source on every make up).
Header comments, README, and .env.example updated to describe the folder/label decoupling.

Verification

docker compose config --format json across all three hosts: every obsidian service resolves OBSIDIAN_VAULT_NAME → /vaults/<name> mount target with the new -wiki bind source; no stray binds; Personal unchanged.
Hosts were make down'd during the folder move, so no container has ever synced against the old path post-move; the recreated containers come up clean.
Entrypoint self-heals wrong ownership on start (per #42), so any root-created bind sources from before the folder move are repaired on first start of the new containers.

## What happened The org wikis moved from `~/<Org>/<Org>-Wiki` to `~/<Org>/-wiki` on every phd-* host, so all eight org wikis now share one literal folder name. The folder name can no longer identify a vault, and the old wiring used it for everything: the host bind source, the container mount target, the remote vault label, and ob's per-vault state key. ## What changed - The compose bind **sources** now point at the new folders (`${OBSIDIAN_VAULTS_BASE}/{Org}/-wiki`). - The bind **targets** and `OBSIDIAN_VAULT_NAME` keep the unique vault labels (`Anthers-Wiki`, `Software-Wiki`, …), which continue to name the remote vault and key ob's per-vault setup state in the shared `obsidian-headless-state` volume. Recreated containers find their existing remotes by label and skip setup as before — no re-link churn, no state reset. - Cross-host safety: a remote labeled exactly with the bare `-wiki` folder name would have cross-linked each vault's folder to the first container's remote; labels avoid that. - Removed the leftover `${OBSIDIAN_VAULTS_BASE}/PhD-Wiki:/vaults/PhD-Wiki` mount dangling under `obsidian-filmmaking-wiki` in all three compose files (the vault was dissolved 2026-10-12 and the entrypoint never synced it — but Docker did auto-create its root-owned bind source on every `make up`). - Header comments, README, and `.env.example` updated to describe the folder/label decoupling. ## Verification - `docker compose config --format json` across all three hosts: every obsidian service resolves `OBSIDIAN_VAULT_NAME` → `/vaults/<name>` mount target with the new `-wiki` bind source; no stray binds; `Personal` unchanged. - Hosts were `make down`'d during the folder move, so no container has ever synced against the old path post-move; the recreated containers come up clean. - Entrypoint self-heals wrong ownership on start (per #42), so any root-created bind sources from before the folder move are repaired on first start of the new containers.

No reviewers

No labels

No milestone

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

parker/cumulus!55

No description provided.

Rows
Columns