Earlier quoted context omitted.
> My only complaint is I wish there was a cheaper paid license. I would love to give back to them for what I'm getting, but > $100/yr/cpu is just too much for what amounts to hobbyist usage. I don't use proxmox anymore at home (1) but as an user I would have loved to pay, say, $5/month and just get access to the updates repository (the stable ones) or maybe something similar. $100/year/cpu was just too much for me as…
My thoughts exactly. Anyone from Proxmox reading? Could it be that you're leaving money on the table here?
Home Lab Beginners guide
351–360 of 400 posts
Re: Home Lab Beginners guide
#352A bit of a tangent but I want to sing the praises of Proxmox for home servers. I've run some sort of Linux server in my home for 25 years now, always hand-managing a single Ubuntu (or whatever) system. It's a huge pain. Proxmox makes it very easy to have multiple containers and VMs on a single hardware device. I started by just virtualizing the one big Ubuntu system. Even that has advantages: backups, high availabili…
As someone still in monolithic home server tech debt I've been meaning to migrate too. The part I always wonder about is storage - said server is a NAS, serving files over SMB and media over Plex. From what I hear some people mount and export their data array [1] directly on Proxmox and only virtualize things above the storage layer, like Plex, while others PCI-passthrough an HBA [2] to a NAS VM. I suppose one advant…
Yep, I do this and it's very simple to give LXCs access to parts of my storage array.
Re: Home Lab Beginners guide
#353> Location For a few years I put mine inside an IKEA FRIHETEN sofa (the kind that just pulls†). Pros: - easy access - completely invisible save for 1 power wire + 1 fiber (WAN) + 1 eth (LAN)†† - structure allows easy cable routing out (worst case you punch a hole on the thin low-end) - easy layout/cable routing inside - noise reduction for free - doubles as warming in winter a seated butt is never cold - spouse enjoy…
I would be really worried about ventilation and heat / fire risk.
Reminds me of the lack rack.
Re: Home Lab Beginners guide
#354Earlier quoted context omitted.
One thing Proxmox is missing (IMHO) is a simple storage sharing system. I ended up just running the kernel NFS server on my Proxmox hypervisor, then sharing disks via a virtual-only LAN to the guest images. Other folks run an NFS server or a full NAS system in a VM under Proxmox. Proxmox' official solution for this is Ceph but that seems like overkill for a small home setup.
Hyperconverged Ceph is both trivial to set up and amazing. Would highly highly recommend it, it makes everything so much easier when your VMs are backed by RBDs.
Re: Home Lab Beginners guide
#355Earlier quoted context omitted.
This is because like many things this is a rich man's hobby. See mechanical keyboards for example.
There's always the $70 IKEA Lack Rack: https://www.instructables.com/The-$70-IKEA-Mini-Server-Rack/
Re: Home Lab Beginners guide
#356Earlier quoted context omitted.
x doubt
Which part? Like, that's what NixOS is. My config repo is declarative, describes in its history every machine I've owned. You could rebuild them at any point in time and get an identical exact machine image out. Idk, this is why it's hard to talk about nix with people that think they know it but then also openly doubt things that you will one day take for granted if you take the time to learn it.
Re: Home Lab Beginners guide
#357Earlier quoted context omitted.
> My only complaint is I wish there was a cheaper paid license. I would love to give back to them for what I'm getting, but > $100/yr/cpu is just too much for what amounts to hobbyist usage. I don't use proxmox anymore at home (1) but as an user I would have loved to pay, say, $5/month and just get access to the updates repository (the stable ones) or maybe something similar. $100/year/cpu was just too much for me as…
My thoughts exactly. Anyone from Proxmox reading? Could it be that you're leaving money on the table here?
No, I do not think we leave much money at the table.
In short, we're targeting enterprise users with a mix of a (soft) stick (e.g. pop-up to note that one isn't having the most production ready experience) a carrot (way better tested updates and depending on the level also enterprise support). Homelab users aren't in the target of our subscription services at all, and if we'd target them with cheap prices that would be just misused by companies too, we know this for a fact because the project is over 15 years old, and there was a lot tried out before getting to the current design. And while there might some protection mechanisms we could set up, we rather avoid DRM'ifying Proxmox projects and avoid wasting time playing cat-and-mouse games with entities trying to abuse this.
Note though, that we still cater to the homelab in other ways even if it isn't our main target audience, like being very active on our community forums for all users, or simple having 100% FLOSS software, no open-core or other, in my opinion rather questionable, open source models. And the price of a pop-up or using the still very stable no-subscription repository is IMO also quite small compared to the feature on gets 100% for free.
If one wants to contribute to our project but either cannot, or does not want, to afford a subscription, then I think helping out in the communities, submitting elaborate bug reports and thought out feature requests, spreading gospel at the companies they work with/for is not only cheaper for them, but also much more worth for the project.
ps. The actual license is the AGPLv3, which is always free, what we sell are subscriptions and trainings for additional services.
Re: Home Lab Beginners guide
#358This article has such a focus on hardware, when that's like... 1% of my homelab decision making. Was hoping this article would delve into hosting your own email, websites and services and the steps to expose them to the public internet (as well as all the requisite security considerations needed for such things). A homelab is just a normal PC unless you're doing homelab stuff.
All of this is very interesting, but not very useful. I'm personally most intrigued by how people are maxing out their old hardware for years, like many examples in this thread
Re: Home Lab Beginners guide
#359I know it's becoming the new "I use arch btw" meme but if you go down this route I highly recommend using nix as the distro. Ideally you can just leave these systems running once they're working and using nix means all your system state is logged in git. No more "wait, how did I fix that thing 6mo ago?" or having to manually put the system back together after a Ubuntu dist upgrade explodes. Every change you've made,…
Same, I originally had a bunch of RasPi's in my lab running differing versions of Raspbian until I got tired of the configuration drift and finally Nixified all of them. Writing a single Nix Flake and being able to build declarative SD card installation images for all of them makes managing a bunch of different machines an absolute dream (tutorial here[0], for those interested). The only issue is remotely deploying N…
Disclaimer: I am a relatively active contributor
Re: Home Lab Beginners guide
#360I'm stuck trying to understand what exactly a home lab is: Apparently a computer at home that has similarities with common production servers? Here's my naive question: What is the point of a home lab, i.e. what makes it better than running stuff on the machine you're developing? I can see some advantages in networking applications (as mentioned in the article), but I have the impression this is not too critical for…
The most important point is to be available all the time in multiple devices that you own, that's why some folks don't want to do these things on their main machines. A laptop you could take it away, and your family at home would/could lose access to the things you're hosting. A beefy desktop might be a bit too power hungry to be on all the time.