Repository navigation

feat: run more than one vault-cortex install on a machine with INSTANCE_NAME - #686

Merged

aliasunder merged 57 commits into

mainfrom

worktree-multi-instance-container-name

Oct 21, 2026

Merged

feat: run more than one vault-cortex install on a machine with INSTANCE_NAME#686
aliasunder merged 57 commits into
mainfrom
worktree-multi-instance-container-name

Commits on Oct 21, 2026
- feat(cli): give each install its own container and volumes with INSTANCE_NAME
  
  aliasunder
  and
  claude
  committed
  e484adb
- feat(remote): add a read-only check for another vault's Sync setup
  
  aliasunder
  and
  claude
  committed
  21f8924
- feat(deploy): name the local Compose project, container and volume after INSTANCE_NAME
  
  aliasunder
  and
  claude
  committed
  aebff96
- docs: describe INSTANCE_NAME and the other-vault check outside the deploy guides
  
  aliasunder
  and
  claude
  committed
  a356c0c
- feat(deploy): name the remote Compose project, container and volumes after INSTANCE_NAME
  
  aliasunder
  and
  claude
  committed
  f459ac2
- feat(remote): stop the boot before syncing another vault's Sync setup
  
  aliasunder
  and
  claude
  committed
  374897b
- docs: add "Run more than one vault" to the local and remote guides
  
  aliasunder
  and
  claude
  committed
  30886d6
- test: expect ShellCheck to cover check-sync-vault
  
  aliasunder
  and
  claude
  committed
  24877a8
- fix(remote): give check-sync-vault's by-hand command the s6 PATH and environment
  
  aliasunder
  and
  claude
  committed
  707ba03
- fix(review): cover PUBLIC_URL and single-volume layouts in the second-vault docs, and list the Sync vault check
  
  aliasunder
  and
  claude
  committed
  b37f13c
- fix(cli): give a remote install the device name of a free --instance-name
  
  aliasunder
  and
  claude
  committed
  b52eecb
- style: clarify instance identity code, Sync vault check comments and second-vault docs
  
  aliasunder
  and
  claude
  committed
  0f91875
- fix: name an unreadable Sync setup answer, reject an empty --instance-name
  
  aliasunder
  and
  claude
  committed
  6c01f45
- test(remote): cover the vault check's remaining branches
  
  aliasunder
  and
  claude
  committed
  c26d41f
- test(cli): pin instance identity exactly and cover its untested paths
  
  aliasunder
  and
  claude
  committed
  22f6dbe
- fix(cli): let init's start replace an existing container with the same name
  
  aliasunder
  and
  claude
  committed
  d8b5a67
- fix: match containers by exact name and fail closed on an unreadable vault list
  
  aliasunder
  and
  claude
  committed
  b2abed0
- fix(cli): offer the next port to a second install instead of 8000
  
  aliasunder
  and
  claude
  committed
  eddbb8a
- fix(cli): read an empty PORT line as the default port
  
  aliasunder
  and
  claude
  committed
  5e852a5
- fix: name an unreadable Sync setup after sync-setup, and follow a carried port
  
  aliasunder
  and
  claude
  committed
  79b4d4e
- fix: show the Sync client's reason when the vault check can't read its setup
  
  aliasunder
  and
  claude
  committed
  db3e7c5
- test: say the init-setup-vault harness copies the script
  
  aliasunder
  and
  claude
  committed
  a1c358a
- fix(cli): read .env values without their quotes, and name a reused remote install's device
  
  aliasunder
  and
  claude
  committed
  d45c1e4
- fix(cli): read an empty memory or daily-notes folder as unset in the settings prompts
  
  aliasunder
  and
  claude
  committed
  e965052
- fix(cli): refuse a re-run of init that renames the install
  
  aliasunder
  and
  claude
  committed
  7532507
- fix(cli): quote the rename hint's folder and say the new name must be free
  
  aliasunder
  and
  claude
  committed
  72c0a76
- fix(cli): report an invalid kept INSTANCE_NAME on a re-run, and say a new name must be free
  
  aliasunder
  and
  claude
  committed
  524035c
- fix(cli): stop an init re-run as soon as the kept INSTANCE_NAME is invalid
  
  aliasunder
  and
  claude
  committed
  bbe16b1
- fix(cli): warn when init can't check names, ask a reused install's port, and read .env like Docker
  
  aliasunder
  and
  claude
  committed
  0117ff5
- fix(cli): patch every Sync token line, drop a remedy init can't keep, and warn only on a real PORT change
  
  aliasunder
  and
  claude
  committed
  c9c7ed7
- fix: let an empty last .env line win, mention --port for a scripted reuse, and correct the setup-error guide
  
  aliasunder
  and
  claude
  committed
  d65c7d9
- fix(cli): read an empty last PORT line as the default port, and a quoted empty token or vault path as unset
  
  aliasunder
  and
  claude
  committed
  2657d9a
- fix(cli): stop start on an empty PUBLIC_URL line, and correct the setup-error guide and a stale comment
  
  aliasunder
  and
  claude
  committed
  042a82d
- fix(cli): treat a quoted whitespace-only PUBLIC_URL as empty, and correct the no-token start comment
  
  aliasunder
  and
  claude
  committed
  2913267
- fix(cli): refuse an invalid PORT, check a remote PUBLIC_URL, and let init start without a Sync token
  
  aliasunder
  and
  claude
  committed
  75c0a91
- fix(cli): keep a localhost PUBLIC_URL with a replaced invalid PORT, and show sign-in steps for a kept .env without a Sync token
  
  aliasunder
  and
  claude
  committed
  50399b4
- fix(cli): check init's .env on disk the way start does, warn about a dropped Sync token, and warn when --port strands PUBLIC_URL
  
  aliasunder
  and
  claude
  committed
  735024c
- fix(cli): name init among resolveDeployment's callers and say when the --port PUBLIC_URL warning fires
  
  aliasunder
  and
  claude
  committed
  6d1adb3
- fix(cli): skip the stranded-PUBLIC_URL warning when the localhost URL already names the new port
  
  aliasunder
  and
  claude
  committed
  5261257
- fix(cli): check a new install's port against the ports other containers publish
  
  aliasunder
  and
  claude
  committed
  6297291
- docs: point multi-vault setup at the settings reference and split the CLI init notes
  
  aliasunder
  and
  claude
  committed
  4133ec0
- docs: point README readers who run more than one vault to the deploy guides
  
  aliasunder
  and
  claude
  committed
  4e1eb1e
- docs: spell out the full CLI commands for updating a second install
  
  aliasunder
  and
  claude
  committed
  7a3abce
- docs: drop the advice to give each install its own DEVICE_NAME
  
  aliasunder
  and
  claude
  committed
  1a3dc28
- docs: say that init suggests the first free port for a second install
  
  aliasunder
  and
  claude
  committed
  c3958af
- docs: keep Compose commands out of the settings text the CLI copies into .env
  
  aliasunder
  and
  claude
  committed
  d505f83
- fix(cli): refuse init over the other mode's install, and fix four review findings
  
  aliasunder
  and
  claude
  committed
  fe0912d
- test(cli): pin the remote daemon-down start gate instead of a removed blank-token skip
  
  aliasunder
  and
  claude
  committed
  b1e3cf8
- fix(cli): refuse a port another container publishes on init re-runs and in the settings list
  
  aliasunder
  and
  claude
  committed
  f068932
- fix(cli): leave a container that runs another image in place
  
  aliasunder
  and
  claude
  committed
  60f5429
- fix(cli): treat the pre-rename vault-mcp image as Vault Cortex
  
  aliasunder
  and
  claude
  committed
  aea2ef3
- fix(cli): keep every container that publishes a host port
  
  aliasunder
  and
  claude
  committed
  5d72a54
- fix(cli): name a free port when --yes stops on a taken one
  
  aliasunder
  and
  claude
  committed
  d3dbbe3
- fix(cli): check the image before logs streams a container
  
  aliasunder
  and
  claude
  committed
  c869498
- fix(cli): fixes from the pre-merge delta review
  
  aliasunder
  and
  claude
  committed
  c9518b8
- docs: say why a docker run install keeps PORT at 8000
  
  aliasunder
  and
  claude
  committed
  a8035a4
- docs: label the docker run paragraph for a second vault like the Updating one
  
  aliasunder
  and
  claude
  committed
  d53c947

Commits

Commits on Oct 21, 2026