this post was submitted on 02 Nov 2025
97 points (92.2% liked)

Selfhosted

52747 readers
670 users here now

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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

In the next ~6 months I’m going to entirely overhaul my setup. Today I have a NUC6i3 running Home Assistant OS, and a NUC8i7 running OpenMediaVault with all the usual suspects via Docker.

I want to upgrade hardware significantly, partially because I’d like to bring in some local LLM. Nothing crazy, 1-8B models hitting 50tps would make me happy. But even that is going to mean a beefy machine compared to today, which will be nice for everything else too of course.

I’m still all over the place on hardware, part of what I’m trying to decide is whether to go with a single machine for everything or keep them separate.

Idea 1 is a beefy machine and Proxmox with HA in a VM, OMV or TrueNAS in another, and maybe a 3rd straight Debian to separate all the Docker stuff. But I don’t know if I want to add the complexity.

Idea 2 would be beefy machine for straight OMV/TrueNAS and run most stuff there, and then just move HA over to the existing i7 for more breathing room (mostly for Frigate, which could also separate to other machine I guess).

I hear a lot of great things about Proxmox, but I’m not sold that it’s worth the new complexity for me. And keeping HA (which is “critical” compared to everything else) separated feels like a smart choice. But keeping it on aging hardware diminishes that anyway, so I don’t know.

Just wanting to hear various opinions I guess.

you are viewing a single comment's thread
view the rest of the comments
[–] solrize@lemmy.ml 6 points 3 days ago (3 children)

Proxmox is a convenient gui wrapper around libvirt but you can do everything without it.

https://wiki.debian.org/libvirt

[–] Creat@discuss.tchncs.de 19 points 3 days ago (3 children)

but you can do everything without it.

yes but why would you? There's a reason we use GUIs, especially when new to a field (like virtualization).

[–] vividspecter@aussie.zone 4 points 3 days ago

yes but why would you?

Mainly because you're required to use their distribution, or to build on Debian, which is not to everyone's liking.

Of course that's an argument against proxmox, and not virt-manager and the like.

[–] solrize@lemmy.ml 2 points 3 days ago

libvirt comes with some gui tool of its own, though I haven't used it. I generally prefer to understand what I'm doing, so I use command line tools or API's at first. GUI's are a convenience to use later, once it's clear how they work.

[–] non_burglar@lemmy.world 1 points 3 days ago

Once you get to know the GUI well enough and start scripting, the GUI becomes less relevant.

This is untrue, proxmox is not a wrapper around libvirt. It has it's own API and it's own methods of running VM's.

[–] hperrin@lemmy.ca 3 points 3 days ago

It’s got more than just VM management, but yeah, it’s a frontend for a bunch of other services, that you don’t need Proxmox for.