IronKrill

I tried it first and swapped away. I know I didn’t like how Radicale required editing text files to add accounts, that’s for sure, but the main reason I swapped was that the Docker environment kept freezing and using up 200% CPU until I manually restarted it. Rinse repeat every few hours. This was on a new install with 1 user. No issues since I moved to Baikal and the web UI is much nicer.

Need is a strong word lol. I definitely don’t need as much as I’ve got as I only use 20-50GB on services (Docker and TrueNAS) with the rest being used as ZFS cache. I would not have bought this much normally but I got it as a package in a PC with an RTX 3080, Xeon Gold 6150, and the RAM for $1000 CAD (750 USD ish?). No way was I passing that up. Image

This survey definitely looks vibe-coded as heck lol but I hope the results will be good.

My results :)

Data Hoarder 💾

• Fleet: 2–3 devices · More than 50 TB
• Motivation: Privacy & data ownership, Independence from Big Tech & subscriptions, Customization & full control
• My MVPs: Immich, Baikal, Forgejo, qBitTorrent, Home Assistant

God knows I wasn’t going to put cost as a motivation… I am actively losing money running double the storage I am using and 100+ GB of RAM on a Xeon chip, but having the headroom is certainly nice and has allowed me to expand as much as I want. Getting a good deal a couple of years back before the price explosion was a huge stroke of luck. If this server ever failed I could figure out a smaller operation with more confidence.

A lot of it is doing what other people tell you to do. This may be encouraging or not, but I consider myself fairly versed in tech and there is still troubleshooting where it feels like trying things at random rather than any skilled insight to a solution. The take-away is it’s okay to skip an app that has terrible documentation and you can’t figure out. Start with something that has good tutorials and if that doesn’t work, try something else. If you can get that up and running those skills will carry over.

Giving away? As in free? Luckyyy

The best thing I did was probably set up Obsidian Live Sync after hearing about it in selfh.st weekly. Compared to the Syncthing setup I had before it is so much quicker, much easier to catch sync errors, and won’t drain my damn phone battery as much! The more things I can move away from Syncthing the better so I will probably be looking at Immich for my photos soon as well.

On the management side, I’ve had my Docker stacks split across Dockhand and Komodo ever since a poorly executed move away from Dockge a few months ago. I finally thought about it and had the time to decide to give up on them both. I like some of the concepts of compose in a git repo and the fancier interfaces, but I just realised it was all over the top for what I need. I missed being able to simply SSH into a damn machine and docker compose up -d in an emergency. Compared to the constant deploy errors of Dockhand and the potential of scrounging application databases for in-DB compose data or attempting to deploy stacks from forgejo when forgejo itself is a stack deployed via git… going back to basic files is a blessing. Lesson learned!

What that culminated in is all my stacks are now in Sencho (which clearly uses a lot of AI code sadly), but it was that or Dockge and I knew Dockge lacked a few things I wanted. The nice thing about Sencho (and Dockge) is that I don’t need either of them because they are based around file-on-disk simple operation. I can cut it out of my setup entirely at any moment and not shed a tear. So much peace of mind leaving Dockhand. Now I just need to find a builder image or write a script to replace Komodo’s build feature because I don’t want to keep using it.

Media watch status no longer persists on media rename. When you move or rename your media files, previously Jellyfin remembered the watch status based on external IDs alone; now it uses an actual reference to the database entry. This is a transitional change and we are working on a better way to handle that in a future version.

I hope they do figure out a solution for that soon… Until that’s fixed I’m going to stay on 10.10.7 for a while.