fix: map x2 route override by folder path
This commit is contained in:
@@ -35,13 +35,15 @@ volumes:
|
|||||||
[syncthing]
|
[syncthing]
|
||||||
api_root = "/var/syncthing"
|
api_root = "/var/syncthing"
|
||||||
local_root = "/data/sync"
|
local_root = "/data/sync"
|
||||||
local_path_overrides = { "/var/syncthing/DownloadsSync-X2" = "/data/qb/Sync" }
|
local_path_overrides = { "/var/syncthing/Downloads/Sync" = "/data/qb/Sync" }
|
||||||
```
|
```
|
||||||
|
|
||||||
Do **not** additionally mount `/srv/downloads/Sync` at a path beneath
|
Do **not** additionally mount `/srv/downloads/Sync` at a path beneath
|
||||||
`/data/sync`. The override is the authoritative mapping for that folder and
|
`/data/sync`. The override is the authoritative mapping for that folder and
|
||||||
keeps qB source files and staging destinations in one mount namespace. Use
|
keeps qB source files and staging destinations in one mount namespace. Use
|
||||||
the folder ID returned by Syncthing's configuration as the override key.
|
the folder's normalized API-visible **path** as the override key (for example,
|
||||||
|
Syncthing `~/Downloads/Sync` becomes `/var/syncthing/Downloads/Sync`); do not
|
||||||
|
use the folder ID.
|
||||||
|
|
||||||
Before starting a stack, validate it with:
|
Before starting a stack, validate it with:
|
||||||
|
|
||||||
|
|||||||
@@ -42,5 +42,5 @@ local_root = "/data/sync"
|
|||||||
# `DownloadsSync-X2` is ~/Downloads/Sync on the host, nested below the qB
|
# `DownloadsSync-X2` is ~/Downloads/Sync on the host, nested below the qB
|
||||||
# root. Resolve it through /data/qb rather than a second nested bind mount so
|
# root. Resolve it through /data/qb rather than a second nested bind mount so
|
||||||
# source staging can hardlink it.
|
# source staging can hardlink it.
|
||||||
local_path_overrides = { "/var/syncthing/DownloadsSync-X2" = "/data/qb/Sync" }
|
local_path_overrides = { "/var/syncthing/Downloads/Sync" = "/data/qb/Sync" }
|
||||||
advertised_addresses = ["dynamic"]
|
advertised_addresses = ["dynamic"]
|
||||||
|
|||||||
@@ -131,8 +131,9 @@ the same client bind mount. This enables hardlinks without creating two Docker
|
|||||||
mount boundaries for the same host files. Do not add a second bind mount for
|
mount boundaries for the same host files. Do not add a second bind mount for
|
||||||
the nested folder: Linux treats it as a distinct mount even when it has the
|
the nested folder: Linux treats it as a distinct mount even when it has the
|
||||||
same `st_dev`, and the client correctly falls back to copy-only capacity
|
same `st_dev`, and the client correctly falls back to copy-only capacity
|
||||||
accounting. See the production deployment README for the required compose and
|
accounting. The override key is the normalized Syncthing folder path beneath
|
||||||
override pattern.
|
`api_root`, not its folder ID. See the production deployment README for the
|
||||||
|
required compose and override pattern.
|
||||||
|
|
||||||
The remaining node examples omit optional `[connection]`, `[jobs]`, and
|
The remaining node examples omit optional `[connection]`, `[jobs]`, and
|
||||||
`[backup]` tables and therefore use these same defaults; deployments may
|
`[backup]` tables and therefore use these same defaults; deployments may
|
||||||
|
|||||||
Reference in New Issue
Block a user