I fuuuhuhuhucking hate this condescending, pestering dark pattern that apparently every single designer on the planet is required to use

Started learning web development.

Totally fair, I agree it is definitely not a good first distro. I think everyone should follow the manual setup process the first time and not use archinstall, because it’s the tutorial which teaches you what’s on your system and how it works.

I’m also not new to the Linux scene, I also run a variety of distros on a variety of machines including servers and I also write software professionally. Arch is fucking great.

I didn’t say it was stable, I specifically said it was unstable. Because it is. I said arch is reliable, which is a completely different thing.

Debian is stable because breaking changes are rare. Arch is unstable because breaking changes are common. In my personal experience, arch has been very reliable, because said breaking changes are manageable and unnecessary complexity is low.

I could not disagree more. Arch is unstable in the meaning that it pushes breaking changes all the time, (as opposed to something like Ubuntu where you get hit with them all at once), but that’s a very different thing from reliability.

There are no backported patches, no major version upgrades for the whole system, and you get package updates as soon as they are released. Arch packages are minimally modified from upstream, which also generally minimizes problems.

The result has been in my experience outstandingly reliable over many years. The few problems I do encounter are almost always my own fault, and always easily recovered from by rolling back a snapshot.

It’s not conventional wisdom, but I’m happiest with arch.

• I’m familiar with it
• can install basically any package without difficulty
• also love that I never have a gigantic version upgrade to deal with. sure there might be some breaking change out of nowhere, but it’ll show up in my rss feeds and it hits all my computers at the same time so it’s not hard to deal with.
• Arch never really surprises me because there’s nothing installed that didn’t choose to put there.
• arch wiki

Tempted by nixos but I CBA to learn it.

lol raid1c10

Oh cool, this is exactly what I was looking for! Thanks :)

Performance is all but irrelevant in this case

It’s a 4gb pi4, think it could boot from ZFS?

I like the DNS on the router idea, I’ll look into it. I do have some split DNS set up as well as adblocking lists (technitium). Not sure what my router can do.

Edit: autocorrect got me

Yeah, I’m getting a pretty strong consensus here that an SSD is the way to go. I’ve also had at least one SD card die on me, and because I didn’t have backups it was pretty inconvenient. Had to recreate my homeassistant setup from scratch.

I get the config only backup, but when I have a mondohuge nas available and we’re dealing with like less than 100 gigs, why not just take a full disk image?

Well, this is my DNS server which means if it’s down the internet is down and I can’t resolve hostnames to ssh into. I know that can be worked around, but I’d really like a quick and easy fix that I could even talk someone through over the phone if I had to.

My real backups are squared away, no worries. Nightly automatic restic snapshots, one to an external drive on this very pi and another to a NAS at my parents’ house.

I’ve also been using BTRFS for awhile, and recently I’ve been getting into zfs which IMO does a better job of handling large software raid arrays. They’re both pretty great!

Yeah, I definitely won’t be buying a new pi anytime soon for exactly that reason but I’ve had this one for awhile and would prefer to do something useful with it.

I have a decent Samsung card in there now, it might survive. Can’t remember what brand the one that failed was, but I don’t tend to buy crappy ones

That’s true, just booting from an SSD would be a lot more reliable and simple.

Bryan „trans people choosing pronouns is like the Picard 4 lights torture scene” Lunduke

• you do not need kubernetes
• you do not need anything to be „high availability”, that just adds a ton of complexity for no benefit. Nobody will die or go broke if your homelab is down for a few days.
• tailscale is awesome
• docker-compose is awesome
• irreplaceable data gets one offsite backup, one local backup, and ideally one normally offline backup (in case you get ransomwared)
• yubikeys are cool and surprisingly easy to use
• don’t offer your services to other people until you are sure you can support it, your backups are squared away, and you are happy with how things are set up.