Chaphasilor [he/him]

Well they said that it should be much, much faster now, so even if it would restart it should be done within a few hours now :)

That’s one big hand…

I’ve gone the TrueNAS SCALE route myself, with TN running on bare metal. All my containers/apps are set up through it, and I’ve also spun up Windows and Linux VMs without major issues, including GPU and USB passthrough.

I do enjoy the security it gives me, will all my apps being versioned/snapshotted regularly and before every update, as well as the rest of my data. Since TN is only using ZFS and not something like MergerFS (which I believe is used by Unraid), the upgrade path is a bit mote restricted. So you should definitely look into your options up-front. For example, you won’t be able to expand a vdev (virtual ZFS disk) later on, you’ll have to create a new one. And you can only use equivalent vdevs to form pools. That means if you start with 3 drives in a vdev for your main storage pool, you can only expand that pool by adding anothet 3 drives with the same capacity as a secons vdev. So make sure you can stomach these costs, or go for fewer and cheaper drives, with a large case.

As for apps, you can set up docker apps easily, and there are a large number of officially or community-maintained apps, where any breaking changes and migrations are handled for you, so updating is a breeze. But you don’t have a much flexibility as with a custom setup. TN has been becoming more generic in that regard though, switching from k3s to regular docker, so you could probably play around with stuff via the CLI without major issues.

Oh and one more thing: you should probably use a separate, dedicated device for Home Assistant. Use a Raspberry Pi or one of their official boards, and you’ll have better support, more features, redundancy, and can still create backups on your NAS via SMB.
Such a second device that is also connected via Tailscale doesn’t hurt either, just in case.

Okay, nice! But now the question is: Does this work with Lidarr on Steroids, so that it can use deemix for both metadata and downloading? ^^

Oh okay! Thanks for letting me know!

how long did it take you to upload this image?

Actually the problem seems to be early adoption, at least that’s what my professor told me. Wealthy countries like the USA and Germany started deploying internet infrastructure very early, and replacing all of this equipment is now very expensive. So we’re mostly stuck with older tech.

“from third countries” probably should’ve been “from third-world countries”

I actually have a friend that uses such a small phone, they use a regular querty keyboard, just usually in combination with glide/swipe typing. I don’t think you can install WearOS keyboards, and afaik the default keyboard on WearOS is a full-size querty anyway…

That’s really awesome! I’ll hold off from trying this for one or two updates, hopefully by then Immich will automatically create albums based on the folder structure as well.
And some solid library sharing feature would also go a long way towards sharing (old) family photos with the whole family!

Immich actually organizes your photos in a simple directory structure, which is customizable (want to group by year? year+month? by day? not at all?). The images are right there in your file system and have the original file name.
The directory is “read-only” though, for the same reason as there is a need to import existing libraries: database synchronization.
Immich offers many features that require a database or pre-processing of files, which makes it fast and feature-rich. If you modify files outside of Immich, it cannot know what changed and loses track of where your media is.

As I said, the (read-only) file structure is always there in case you want to switch.

Why would you be “dependent” on it in any way? There’s no vendor lock in…

Is sonarr/radarr a hard requirement? Would be interested in just using this as an alternative frontend for jellyfin