Then you need a third application (e.g. syncthing) to replicate the auto upload functionality of Nextcloud.
Personally I don’t want to have same functionality in a different stack because of pipeline issues. Doesn’t solve OPs issue I just wanted to point out that your solution might have drawbacks OP didn’t see at first glance :)
Makes sense, thanks for pointing it out!
That’s not how I would get a discography, a non YouTube artist (some international ones), a whole album or lossless though - or am I mistaken?
Why did you opt for a setup with 2.5" disks? I ask because I just replaced my track server because the 2.5" are just more expensive than a server replacement plus 3.5" disks where I’m from (with 4x10tb).
Thank you! That’s really interesting, the performance with a pi 3 was way worse - even more than the pure spec difference would’ve lead me to believe.
The OCR devs have made a really awesome job!
You are running a specific module of a project locally - not the whole project. The web server is an integral part - leaving it out makes you do a bit of the leg work: you’d need to figure out how the websites get built and deployed and then reverse engineer that for your android environment.
Personally I’m fascinated by that attempt and it could be an awesome learning opportunity. To be honest I don’t have the motivation to follow your path down this rabbit hole though.
If you decide to follow up I’d appreciate you giving updates from time to time about your insights! ♥
Thanks for sharing! The only thing I’m surprised to see in your list is paperless - how long does OCR take on a pi?
“Being a router” is what they are good for! Even needed.
Edit to be more specific: two switches in each of the 10gbit and redundant uplink would be a setup I can see, depending on your line.
No overkill there :)
Have exactly the same setup:
It tunnels everything that is bound to the same network (see the line with gluetun within the qbittorrent container.
And for anyone using a reverse proxy: that can run against the gluetun container with the bound containers port. (edit: in OPs example gluetun:8090 for qbittorrent web)
Why a limit at all? I see it as our role to share just as we received it from others who shared with us.
If space is needed remove the ones with the lost existing seeders instead of some ratio goal.
Keep each torrent alive!
I didn’t know that about the immich app, thanks for pointing it out!