fix: swam synology directory to raspberry pi

.env.sample

@@ -85,6 +85,8 @@ TECHNITIUM_ALLOW_BLOCKING_REPORT=false
 TECHNITIUM_PREFER_IPV6=false
 TECHNITIUM_MEM_LIMIT=512m
 TECHNITIUM_MEM_RESERVATION=192m
+# Local persistent data path for Technitium on Pi (bind mount)
+TECHNITIUM_CONFIG_DIR=./appdata/technitium
 
 # Dockhand
 DOCKHAND_ENCRYPTION_KEY=
@@ -92,7 +94,9 @@ DOCKHAND_PORT=3000
 DOCKHAND_BIND_IP=0.0.0.0
 DOCKHAND_MEM_LIMIT=256m
 DOCKHAND_MEM_RESERVATION=64m
+# Local persistent data path for Dockhand on Pi (bind mount)
+DOCKHAND_DATA_DIR=./appdata/dockhand
 # Host path containing compose stacks that Dockhand should manage
-DOCKHAND_STACKS_DIR=/opt/stacks
+DOCKHAND_STACKS_DIR=./stacks
 # Find with: stat -c '%g' /var/run/docker.sock
 DOCKER_GID=999

dns/end-to-end-migration-runbook.md

@@ -38,8 +38,10 @@ Expected:
    - `DNS_BIND_IP=192.168.60.6` (temporary during staging)
    - `TECHNITIUM_ADMIN_PASSWORD=<strong-password>`
    - `DOCKHAND_ENCRYPTION_KEY=<long-random-string>`
+   - `TECHNITIUM_CONFIG_DIR=./appdata/technitium`
+   - `DOCKHAND_DATA_DIR=./appdata/dockhand`
    - `DOCKER_GID=<docker.sock group id>`
-   - `DOCKHAND_STACKS_DIR=<path you want Dockhand to manage>`
+   - `DOCKHAND_STACKS_DIR=./stacks` (or local path you want Dockhand to manage)
 2. Render the compose from template:
 ```bash
 ./substitute_env.sh docker-compose-files/technitium-dockhand_template.yaml docker-compose-files/technitium-dockhand.yaml .env

dns/technitium-dockhand-deployment.md

@@ -12,7 +12,9 @@ Update your `.env` with these required values:
 - `DNS_BIND_IP=192.168.60.5`
 - `TECHNITIUM_ADMIN_PASSWORD=<strong-password>`
 - `DOCKHAND_ENCRYPTION_KEY=<long-random-string>`
-- `DOCKHAND_STACKS_DIR=<host path containing compose files>`
+- `TECHNITIUM_CONFIG_DIR=./appdata/technitium`
+- `DOCKHAND_DATA_DIR=./appdata/dockhand`
+- `DOCKHAND_STACKS_DIR=./stacks` (or any local host path containing compose files)
 - `DOCKER_GID=<docker.sock group id>`
 
 For 2GB Pi 4 (recommended defaults already in `.env.sample`):
@@ -23,6 +25,12 @@ For 2GB Pi 4 (recommended defaults already in `.env.sample`):
 
 Tip:
 - `DOCKER_GID` command: `stat -c '%g' /var/run/docker.sock`
+- Relative bind paths (like `./appdata/...`) are resolved from the folder containing the rendered compose file (`docker-compose-files/`).
+
+Create local bind-mount folders:
+```bash
+mkdir -p docker-compose-files/appdata/technitium docker-compose-files/appdata/dockhand docker-compose-files/stacks
+```
 
 ## 2) Render compose from template
 Run:

docker-compose-files/technitium-dockhand_template.yaml

@@ -1,9 +1,4 @@
 version: '3.8'
-
-# Technitium DNS + Dockhand stack
-# - Technitium replaces Pi-hole + Unbound behavior (blocking + recursion)
-# - Dockhand manages container stacks from a web UI
-
 services:
   technitium-dns:
     image: technitium/dns-server:latest
@@ -34,7 +29,8 @@ services:
       DNS_SERVER_WEB_SERVICE_HTTP_PORT: "{{TECHNITIUM_WEB_CONTAINER_PORT:-5380}}"
     volumes:
       - /etc/localtime:/etc/localtime:ro
-      - {{DOCKERCONFDIR}}/technitium:/etc/dns
+      # Local persistent config path for Raspberry Pi deployments
+      - {{TECHNITIUM_CONFIG_DIR:-./appdata/technitium}}:/etc/dns
     ports:
       # Core DNS service
       - "{{DNS_BIND_IP:-0.0.0.0}}:53:53/udp"
@@ -73,8 +69,10 @@ services:
       - "{{DOCKER_GID:-999}}"
     volumes:
       - /var/run/docker.sock:/var/run/docker.sock
-      - {{DOCKERCONFDIR}}/dockhand:/opt/dockhand
-      - {{DOCKHAND_STACKS_DIR:-/opt/stacks}}:/opt/stacks
+      # Local persistent config path for Raspberry Pi deployments
+      - {{DOCKHAND_DATA_DIR:-./appdata/dockhand}}:/opt/dockhand
+      # Host folder containing compose stacks Dockhand should manage
+      - {{DOCKHAND_STACKS_DIR:-./stacks}}:/opt/stacks
     ports:
       - "{{DOCKHAND_BIND_IP:-0.0.0.0}}:{{DOCKHAND_PORT:-3000}}:3000/tcp"
     mem_limit: "{{DOCKHAND_MEM_LIMIT:-256m}}"