Nicely done! Do you perchance have any hi res version?
Perhaps you could be interested in Tdarr, so you can transcode your media files to formats you can directly consume in your different devices.
That could save you the need to buy new hardware for on-the-fly work, and also give you control about the metadata, audio tracks and subs included in the final file.
sniffff They grow up so fast... :')
Welp, time to start looking for alternatives...
Can't blame the dev for wanting to cash out on his work, but I am not going to keep using apps that will get ridden with ads and trackers.
I believe you meant "excellent"...
Autocorrect, amirite?
In regards to productivity, you could also take a look at Get Things Done or Bullet Journal as time/task organization frameworks, or Zettelkasten if you need data/knowledge organization.
What about going to a metal workshop and asking if they can make a replica of the aluminum piece but in copper, with a really polished finish?
Might even ask them to make it a little wider to spread the heat, if it fits inside the case.
Second this, it's my daily driver on android to control my qBittorrent instance, and so far I haven't missed any kind of functionality, it just does everything I need.
Aw yissss... About time!
Holy... This is one of the most deranged things I've ever read...
I had to stop reading 3/4 of the way, I couldn't take the craziness anymore.
I second OVH, been using their services for the best part of 2 decades now, and I can't see myself migrating out unless something big happens.
I really love the ease of editing DNS zones and the free dynamic DNS with your domains. A self-hoster delight, for sure.
You cannot reference a part of a docker-compose file from another, but you can have an .env file alongside them where you can declare variables in the format NAME=VALUE, and reference that in the dc files with ${NAME}, assuming your dc files reside alongside each other (with different names) and the .env file itself. I have done this before.
I cannot say if that will work for your use case, as I haven't tried to use the same docker volume in different containers. I don't even know if that is possible, given the possibility of conflicts if both containers tried to access the same files, something to test out, for sure.