@FrazzledBrynn I had my first laser session last week, and yep. That smell.
Bad takes, tech, music, cocktails, comma-delineated profile bios.
they/them.
Sydney, Australia.
| Github | https://github.com/simonxciv |
simon
- 33 Followers
- 99 Following
- 115 Posts
@cassidy @MishaalRahman 16's labels have clearer contrast, too. To my eyes, it's not just more precise, but more readable, too
@zak once more I am wishing we could just mute america
@zak this is one of my "favourite" fediverse features. So many posts have invisible replies like this, and nobody's been able to tell me why. Also, I once got yelled at by a fossbro (a stranger, not even a mutual) saying I should PR a fix if I care enough to post about it. The culture here can be so abrasive, and the bugs are so often showstoppers.
@zak glad I could help! the learning curve on self hosting can be pretty steep, and it's made extra daunting by the amount of spend required at the start, but once you've settled on a direction, you kind of figure it out as you go, and there's no single correct way to do it. I lean towards a more hands-off setup, because I'm realistic about how much of my free time I'm willing to spend on tinkering, but others like a higher level of control and granularity than that. You'll find your groove as you go!
@zak I have colleagues who run essentially the same setup, but with an Intel NUC (or similar small form-factor PC) for the applications. From what it sounds, your HTPC would be a good candidate for that!
@zak I have a Synology 1819+. It's a few years old now, but running solidly. As far as performance goes, I don't really care much as it's literally just for storage. All of the relevant applications run on my workstation in Podman containers, with the NAS shares mounted over NFS.
Separating concerns this way makes sense for me. Keeping applications and storage separate means I can treat the NAS like a dumb appliance, and my workstation with its beefy CPU and GPU (for hardware transcoding) can handle all the actual work.
@zak both RAID and backblaze management are made significantly easier with Synology's nice GUI for managing both, so I'll admit my general knowledge on setting up/configuring either under Linux generally isn't great 😅 backblaze is Amazon S3 compatible, so there are a lot of guides available to help with that at least.
Call it pragmatism or laziness, but I have a full-time job already, I don't want to be a sysadmin in my own home as well!
@zak an IronWolf Pro will last you for years. They've got really generous warranties, and are built for 24/7 operation. I personally wouldn't go with anything else at this point.
On a side note, have you thought about your backup strategy yet? It'll definitely be easier to have that in place before your collection has grown to the point where backing up becomes painful 😅
The parts of my collection that would be impossible to replace are just the Photos and Music libraries, so the setup I run is basically:
- RAID6 for two drive failure resilience in my NAS
- rsync from my NAS to an archive on my server
- backblaze cloud backup
If I have a catastrophic failure and lose my movies and shows, I'll be annoyed but not upset, but my music and photos would be devastating, so two backups of those, and drive redundancy otherwise works for me.
@zak I can't provide much help with enclosures (I use a Synology NAS + a dedicated server for the actual apps), but I've been using Seagate IronWolf Pro drives for a few years now, after I had a couple of Western Digital drives fail (and the more recent WD SMR/CMR shenanigans). The IronWolf Pros are rock solid though, if a little pricey. IIRC the 22TB drives offer the best $/GB value at the moment, though I'm sure the 24TB drives will come down in price over time.
Also, it's probably a good time of year to buy them. Lots of end-of-year and boxing day sales (at least here in my part of the world).