1f1e3ff6b4
Merge pull request 'Allow serienen/videoen categories in movetdarr' ( #5 ) from fix/movetdarr-en-categories-20260916 into main
2026-09-16 11:55:25 +02:00
Trulla
5b4dd2384e
Allow serienen/videoen categories in movetdarr
...
Die Kategorie-Whitelist kannte nur serien4k|serien|video4k|video. Die
englischen Arr-Instanzen sonarrEN (Port 8991, Root /data/FHD/serienen) und
radarrEN (Port 7880, Root /data/FHD/videoen) nutzen aber serienen/videoen.
Folge: Downloads dieser Kategorien wurden mit "nicht unterstuetzte Kategorie"
abgewiesen und blieben in /usenet/complete liegen, ohne je in den
FileFlows/Arr-Flow zu gelangen. Gefunden: Mutiny.2026 x2 (08./09.09.2026,
zusammen ~21 GB), beide Filme in radarrEN weiter monitored/hasFile=false.
/tdarr/complete/{serienen,videoen} existieren bereits; die FileFlows-Library
scannt /tdarr/complete rekursiv, es braucht also nur die Whitelist.
2 neue Testfaelle (serienen + videoen), test_movetdarr.py und
test_movetdarr_parallel.py gruen.
2026-09-16 11:55:01 +02:00
64892fadb1
Merge pull request 'movetdarr v5: lease lock on local filesystem' ( #4 ) from fix/movetdarr-nfs-lock into main
2026-09-07 11:38:41 +02:00
35efa23cde
tests: FD-lock serialization and NFS regressions
2026-09-07 11:38:34 +02:00
e0d59f213c
tests: isolate LEASE_LOCK per temp dir for v5
2026-09-07 11:38:29 +02:00
32d68201fd
movetdarr v5: FD-based lease lock on local /config filesystem (NFS flock fix)
2026-09-07 11:38:28 +02:00
bb748741cd
fix(movetdarr.sh): BusyBox flock hat kein -w (timeout) → -n + Retry-Loop
...
BusyBox flock kennt nur -n (non-blocking), nicht -w/--timeout.
Der alte Code 'flock -w 900' schlug fehl → Skript fiel sofort in
'fahre ohne Lock fort' und lief ohne Race-Schutz.
Fix: -n mit 900s Retry-Loop (1s Intervall) = effektiv 15min Timeout.
Der Lock wird jettt korrekt gesetzt, parallele Downloads sind serialisiert.
2026-09-06 10:10:37 +02:00
e8a36502e9
movetdarr v4: flock-Serialisierung gegen n8n-staticData-Race bei parallelen SAB-Auftraegen
2026-09-05 18:48:42 +02:00
71247af6b6
Merge pull request 'fix: wait for every file in season packs' ( #3 ) from fix/media-handoff-season-packs-20260905 into main
2026-09-05 08:20:54 +02:00
7266c64bac
fix: wait for every file in season packs
2026-09-05 08:20:53 +02:00
90de3a31fd
fix: wait for every file in season packs
2026-09-05 08:20:52 +02:00
20530d71b8
Merge pull request 'fix: deploy movetdarr from Git before SAB starts' ( #2 ) from fix/git-sync-movetdarr-20260905 into main
2026-09-05 08:17:00 +02:00
36589088f4
fix: deploy movetdarr from Git before SAB starts
2026-09-05 08:16:59 +02:00
cebfa13026
Merge pull request 'feat: keep SAB jobs leased until Arr import' ( #1 ) from feat/media-handoff-orchestrator-20260905 into main
2026-09-05 07:59:58 +02:00
0ce5a817a2
feat: keep SAB jobs leased until Arr import
2026-09-05 07:59:56 +02:00
6694b48420
feat: keep SAB jobs leased until Arr import
2026-09-05 07:59:56 +02:00
sascha
9373aef95e
movetdarr.sh v2: FileFlows-Leichen-Handling + Fehler-Reporting (SAB PostProcessing Fix 05.09.2026)
2026-09-05 00:03:43 +02:00
0ae625d00a
feat: SABnzbd VPN-Exit ueber dedizierten Hetzner-Tunnel wiederherstellen
...
- wireguard-Service (sabnzbd-wg) zurueck in den Stack
- sabnzbd nutzt network_mode: service:wireguard (Full-Tunnel ueber Hetzner-IP)
- healthcheck auf wg-handshake + depends_on service_healthy
- Port 7777 am wireguard-Container (geteilter Netzstack)
Tunnel: SABnzbd 10.13.13.2 <-> Hetzner wg2 (51821), frische Keys + PSK,
isoliert vom wg0-Hub. Behebt: Usenet lief ungeschuetzt ueber RZ-IP.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-15 21:52:47 +02:00
sascha
3a017e9f67
feat: mergerfs Bind-Mount statt Docker NFS-Volume
2026-05-01 18:28:45 +02:00
sascha
97b6db4d0c
feat: add sops+age secrets encryption
2026-04-04 09:43:37 +02:00
feldjaeger
75f9a64875
chris
2026-03-29 15:17:52 +02:00
41700100d8
Update compose.yaml
2026-03-27 16:02:19 +01:00
135f9303d6
Update compose.yaml
2026-03-27 15:56:54 +01:00
5481210e60
Update compose.yaml
2026-03-26 22:20:21 +01:00
8a6ed6fe74
Update compose.yaml
2026-03-02 17:24:31 +01:00
93492acf4e
Update compose.yaml
2026-03-02 16:32:17 +01:00
d75f88f69b
Update compose.yaml
2026-03-02 16:22:44 +01:00
7084df0b4b
Update compose.yaml
2026-03-02 16:20:23 +01:00
c64d4808a4
Update compose.yaml
2026-03-02 15:56:55 +01:00
bd4ebf1e14
Update compose.yaml
2026-03-02 15:55:19 +01:00
komodo
a29a2d1286
[Komodo] admin: Write Stack File: update compose.yaml
2026-03-02 06:40:11 +01:00
komodo
291a013d07
[Komodo] admin: Write Stack File: update compose.yaml
2026-03-02 06:38:56 +01:00
komodo
13a5dc23d8
[Komodo] admin: Write Stack File: update compose.yaml
2026-03-02 06:34:47 +01:00
komodo
361852fa23
[Komodo] admin: Write Stack File: update compose.yaml
2026-02-07 14:18:29 +01:00
komodo
12f9f81b7e
[Komodo] admin: Write Stack File: update compose.yaml
2026-02-07 14:18:19 +01:00
komodo
5ecc810ce7
[Komodo] admin: Write Stack File: update compose.yaml
2026-02-07 14:11:11 +01:00
komodo
43cf47848a
[Komodo] admin: Write Stack File: update compose.yaml
2026-02-07 14:06:52 +01:00
komodo
783b994eb6
[Komodo] admin: Write Stack File: update compose.yaml
2026-02-07 13:54:11 +01:00
komodo
365b0827fd
[Komodo] admin: Write Stack File: update compose.yaml
2026-02-07 13:48:55 +01:00
komodo
62f2554294
[Komodo] admin: Write Stack File: update compose.yaml
2026-02-07 13:47:14 +01:00
komodo
a2e02af037
[Komodo] admin: Write Stack File: update compose.yaml
2026-02-07 13:46:52 +01:00
f7fd84ab1f
Create compose.yaml
2026-02-07 13:42:38 +01:00
