Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
OK, but why?
Well, for fun and as a cool hobby project, I get that. That is enough to justify it, like any other crazy hobbyist project. Don't let me stop you.
But in the spirit of practicality and speaking hypothetically: Why set it up that way?
For self-hosting why not build a few standalone machines and run off that instead? The reason to do this large scale is optimizing resources so you can assign a smaller pool of hardware to users as they need it, right? For a home set of two or three users you'd probably notice the fluctuations in performance caused by sharing the resources on the gaming VMs and it would cost you the same or more than building a couple reasonable gaming systems and a home server/NAS for the rest. Way less, I bet, if you're smart about upgrades and hand-me-downs.
Maybe my situation is just unique, but due to my job I'm able to have a single workstation with multiple high VRAM GPUs. I wouldn't be able to justify the cost of buying new GPUs and an entire rig just for gaming or AI image/video. I wouldn't foresee more than 2 VMs using the GPU in high priority at any single time.
When I'm not working this system sits idle or is running renders. Why not utilize the amazing resources I have to serve my other needs?
OK, yeah, that makes sense. And it IS pretty unique, to have a multi-GPU system available at home but just idling when not at work. I think I'd still try to build a standalone second machine for that second user, though. You can then focus on making the big boy accessible from wherever you want to use it for gaming, which seems like a much more manageable, much less finicky challenge. That second computer would probably end up being relatively inexpensive to match the average use case for half of the big server thing. Definitely much less of a hassle. I've even had a gaming laptop serve that kind of purpose just because I needed a portable workstation with a GPU anyway, so it could double as a desktop replacement for gaming with someone else at home, but of course that depends on your needs.
And in that scenario you could also just run all that LLM/SD stuff in the background and make it accessible across your network, I think that's pretty trivial whether it's inside a VM or running directly on the same environment as everything else as a background process. Trivial compared to a fully virtualized gaming computer sharing a pool of GPUs, anyway.
Feel free to tell us where you land, it certainly seems like a fun, quirky setup etiher way.