From 62cbea71411c587853f819952ec016c118e4e502 Mon Sep 17 00:00:00 2001 From: FailedProxy Date: Sun, 10 May 2026 19:39:10 -0400 Subject: [PATCH] updated to do --- Notes_To-Do.md | 45 ++++++++++----------------------------------- 1 file changed, 10 insertions(+), 35 deletions(-) diff --git a/Notes_To-Do.md b/Notes_To-Do.md index 3869ee9..0613a3d 100644 --- a/Notes_To-Do.md +++ b/Notes_To-Do.md @@ -7,47 +7,17 @@ claude -━━━ ⚙️ Setup ━━━ -━━━ 🌐 Lidarr API ━━━ -━━━ 🎬 Albums ━━━ -━━━ 🎬 Artists ━━━ - -━━━━━ 📋 LIDARR MISSING ART SUMMARY ━━━━━ -🖥️ Identity: HOST1 (unRAID-Gmer4Lfe) -⏱️ Duration: 21s -🎬 Albums: 8050 checked, 0 already complete -🎬 Artists: 1099 checked, 0 already complete -🏁 Status: ✅ ALL DONE -━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ -Script Finished May 08, 2026 19:50.06 +❯ now we should be able to allow or have other host be able to start a shared srvice if desired using + shared auth stack, maybe a container array in host*.conf folder that can add the container to the other + servers, just thinkig of future design - - - - - - - -arrs system error, can we delete movies from radar when dropped from tmdb, 99% of the time its future movies that get dropped -movie Silent Hill 2: The Movie (tmdbid 466226) was removed from TMDb. same logic for sonarr. - - - - - -failback hand back needs to happen in stages and in reverse...... so if i hit tier 3, i want it to only stop the services in tier 3 then rsync, then hand abck, then tier 2, shutdown containers rsync, and handback, same for 1.... this will allow emby to stay up during possible long writebacks. and ensure all data is sill synced back before emby is handed back with minimal user downtime - - - - -later. . fix failover strike list timing, maybe 30 seconds. them a t 90 seconds 3 stike triggers. just gotta test buffer. never had the strike system . verify silent toggle switches back on good notifications @@ -62,10 +32,15 @@ later. WAY LATER -when a user offboards and there is more than 1 server left, one needs to become the owner, we could do this in multiple ways or a combination, strongest server and BANDWIDTH,whos contributing more.... maybe we just promt and ask them + +now we should be able to allow or have other host be able to start a shared srvice if desired using + shared auth stack, maybe a container array in host*.conf folder that can add the container to the other + servers, just thinkig of future design + + +when a owner offboards and there is more than 1 server left, one needs to become the owner, we could do this in multiple ways or a combination, strongest server and BANDWIDTH,whos contributing more.... maybe we just promt and ask them -rsync, look into cross sync. newest timestamp wins, so if a show 1 updates on server 1, show 2 on server 2, show 3 on server3, when rsync runc, each machine would run this, and add remove based on time stamp, and have arrs pull after sync