Same, in fact you can also went down in RPi models. Basically the more you know, the less you need, e.g. going from Plex to Kodi to minidlna...
this post was submitted on 07 Feb 2025
952 points (98.6% liked)
linuxmemes
22371 readers
1355 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
- Don't get baited into back-and-forth insults. We are not animals.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
- These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudoin Windows. - No porn. Even if you watch it on a Linux machine.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
5. π¬π§ Language/ΡΠ·ΡΠΊ/Sprache
- This is primarily an English-speaking community. π¬π§π¦πΊπΊπΈ
- Comments written in other languages are allowed.
- The substance of a post should be comprehensible for people who only speak English.
- Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed. Β
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
founded 2 years ago
MODERATORS
I had to buy a lenovo thinkcentre mini because was cheaper than a brandnew raspberry pi.
I have literally been on this exact journey. Mind you I'm on NixOS across two boxes so not quite a raspi... Perhaps my downsizing is not yet complete
I've discovered that there are a lot of medium-tier software engineers who immediately will go straight to horizontal scaling (i.e: just throw hardware at it), and I've seen instances where very highly skilled engineers just write their code better, set things up on a bare metal server, cache things, etc. and manage with just a single badass server
Even just the choice of programming language makes a big difference. Running a JVM language or NodeJS, Python, Ruby etc., you can be bottlenecked by a Pi. Meanwhile, Rust or C/C++ will use barely a fraction of those resources.
load more comments
(1 replies)
Absolutely the best way to learn though. The number of places I've walked into that had no clue about containers or even a vpc and thought Google drive was an API is too damn high.
I have actually had to write something that used the Google drive API for a friend's company once and it was... Unpleasant. Counterintuitive. Woefully inconsistent. My solution worked but it sucked and I am a bit ashamed of it
load more comments
(1 replies)
Yup, a pi is enough for me.
Well... 5 Pis and an ancient NUC running proxmox are enough for me. And a DS920+... and an old laptop running docker are enough for me.
Yes, you can optimize a lot. Especially with Linux. I did the same and even started to replace program that did too much, bloated, with my own programs. To speed up the development I did it with AI and Cursor.
With Linux any old computer from yesteryear can become a quick server. That's what I do, just make sure you got backups.
I've literally tossed working computers of the exact same model as my home server into the ewaste bin at work. One person's trash and all
load more comments
(4 replies)
I spend all day at work exploring the inside of the k8s sausage factory so I'm inured to the horrors and can fix basically anything that breaks. The way k8s handles ingress and service discovery makes it absolutely worth it to me. The fact that I can create an HTTPProxy and have external-dns automagically expose it via DNS is really nice. I never have to worry about port conflicts, and I can upgrade my shit whenever with no (or minimal) downtime, which is nice for smart home stuff. Most of what I run tends to be singleton statefulsets or single-leader deployments managed with leases, and I only do horizontal for minimal HA, not at all for perf. If something gives me more trouble running in HA than it does in singleton mode then it's being run as a singleton.
k8s is a complex system with priorities that diverge from what is ideal for usage at home, but it can be really nice. There are certain things that just get their own VM (Home Assistant is a big one) because they don't containerize/k8serize well though.
Yup, same here. being able to skip all the networking and DNS hassle and have it automated for you is so nice.
Having databases fully managed with cnpg is AMAZING
I just have renovate set to auto update my argocd, so everything just runs itself with zero issues. Only the occasional stateful container that has breaking changes in a minor version.
If something OOMs or crashes, it all just self heals, I never need to worry about it. I don't have any HPAs (nor cluster scaling obv), though I do have some HA stuff set up just to reduce restart times and help keep the databases happy.
The main issue with Kubernetes is that a lot of self-hosted software makes bad design decisions that actively make kubernetes harder, eg sqlite instead of postgres and secrets stored in large config files. The other big issue is that documentation only supports docker compose and not kubernetes 90% of the time so you have to know how to write yaml and read documentation.
Moving my hass from a statefulset to kubevirt sounds tempting. Did you have better reliability/ergonomics? I have been looking into moving my Hass automation to NodeRed, so that I can GitOps it all, since NodeRed supports git syncing.