An access has an id, and its mounts name it (issue 153)

Ten definitions name each access by id; the path stays as the default an assignment may replace,
and the host side of every mount says ${access:<id>}. Resolved with no placement, every definition
names exactly the paths it named before (TestPlacedDirectoriesKeepTheirPaths, extended). On an
adopted machine the assignment now says `accesses: {<id>: <path>}` and the mount follows.

Needs the controller that knows an access id (mesh-controller #176); the running one refuses the
field at registration.
This commit is contained in:
2026-10-01 00:01:42 +02:00
parent 34ccc457fa
commit 684b9853ad
10 changed files with 44 additions and 22 deletions
+2 -1
View File
@@ -25,6 +25,7 @@
],
"accesses": [
{
"id": "downloads",
"path": "/services/media/downloads",
"mode": "read-write"
}
@@ -58,7 +59,7 @@
],
"volumes": [
"/services/qbittorrent/config:/config",
"/services/media/downloads:/downloads"
"${access:downloads}:/downloads"
]
},
{