Migrating from the old layout
The old D:\Docker tree grew one convention per service (Builds\IdentityServer\.env.All*,
mounted-configs\..., Run\segmentation-server, Nginx Proxy Manager). The stack layout
gives every stack the same shape (Host layout). Moving over is a copy, not a rename: old
files stay where they are until you delete them.
Hosts set up from nornir-docker/deploy
The deploy tooling moved from nornir-docker/deploy/ to the connectomes-deploy repository on 2026-10-21; the copy left in
nornir-docker/deploy/ is no longer maintained. On a host whose layout was created from the old
copy:
clone connectomes-deploy (
/srv/connectomes-deployon Ubuntu, next to the other checkouts on Windows);re-run its
Initialize-DockerHost.ps1with the host’s role and-SetUserEnv; it rewrites<root>/stack.ps1to forward to the new checkout and copies only templates that are missing;add
DEPLOY_REPO_ROOT_HOST=<that checkout>toRun/_host/host.env(the script fills the key only when it is already present and empty);on the dev box, add
DEPLOY_REPO_ROOT_HOSTto each target’sReposintargets.psd1so-Syncupdates it;compare existing run env files with the current templates, then
stack.ps1 doctor.
Copy files with Move-DockerHostLayout.ps1
The script is in the connectomes-deploy
repository. Always run with -WhatIf first; it prints the old-to-new table without copying:
D:\src\git\connectomes-deploy\Move-DockerHostLayout.ps1 -WhatIf
D:\src\git\connectomes-deploy\Move-DockerHostLayout.ps1
D:\src\git\connectomes-deploy\Move-DockerHostLayout.ps1 -From D:\Docker -To \\newserver\c$\srv\docker
It never deletes or overwrites. Env files that map to one <stack>.run.env are concatenated
with a header naming each source; when a destination already exists it writes
<dest>.migrated next to it for you to diff and merge. Old mounted-configs\nornir-build-*
sessions are left alone unless you pass -IncludeWork. Then:
Initialize-DockerHost.ps1 -Role <role>(creates the rest of the tree and the forwarding launchers);compare each migrated env file with its
example.<stack>.run.envand rename keys (the script does not rename variables);stack.ps1 doctor;on the dev box, stop the old all-in-one
vikingcompose project before the firststack.ps1 ... up(docker compose -p viking down); its published ports clash with the new stacks;delete the old files once the stacks run.
Old to new
Old |
New |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
copied to |
|
|
|
|
|
|
|
forwarding launchers written by |
|
|
|
|
Removed scripts and files
Removed ( |
Use instead |
|---|---|
|
connectomes-deploy |
|
|
|
built into |
|
|
|
|
|
|
|
|
|
|
|
nothing; images install from the monorepo and |
|
the |
|
|
|
connectomes-deploy |
Kept on purpose: docker-run-nornir-dev.ps1 (used by D:\Docker\Run\nornir-dev\run.ps1),
Cleanup-CursorWorkerClones.ps1 (its -AgentCloneParent default now matches
start-cursor-worker.ps1), windows-docker-layout/Initialize-NornirCursorWorkerLayout.ps1
(worker only), and nd-build.ps1 / nd-build.cmd.
Renamed variables
Old |
New |
|---|---|
|
|
|
|
Viking service keys that changed with the move to Run/<stack>/ are listed in the Viking
deployment docs.
Behaviour changes worth knowing
Launchers under
Builds\nornir-buildused to be copies and broke aftergit pull; they are now forwarding launchers.nornir-buildjoinsnornir-dashboard_defaultautomatically and publishes tomosquitto(the old default network name did not match the compose project).nornir-buildpasses--shm-size=64gby default.The TEM scripts choose NumPy automatically when no GPU is present.
compose.cursor-dev.yamlloadsnornir-docker/.envwithenv_file, so settings such asNORNIR_SYNC_REMOTEreach the container without editing the compose file.