this post was submitted on 14 Jun 2023
3 points (100.0% liked)

Self Hosted - Self-hosting your services.

11587 readers
25 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

Important

Beginning of January 1st 2024 this rule WILL be enforced. Posts that are not tagged will be warned and if not fixed within 24h then removed!

Cross-posting

If you see a rule-breaker please DM the mods!

founded 3 years ago
MODERATORS
 

So, I’ve been self-hosting for decades, but on physical hardware. I’ve had things like MythTV and an asterisk voip system, but those have been abandoned for years. I’ve got a web server, but it’s serving static content that’s only viewed by bots and attackers.

My mail server, that’s been active for more than two decades is still in active use.

All of this makes me weird in the self-hosted community.

About a month ago, I put in a beefy system for virtualization with the intent to start branching out the self hosting. I primarily considered Proxmox and xcp-ng. I went with xcp-ng, primarily because it seems to have more enterprise features. I’m early enough in my exploration that switching isn’t a problem.

For those of you more advanced in a home-lab hypervisor, what did you go with and why? Right now, I’m pretty agnostic. I’m comfortable with xcp-ng but have no problems switching. I’m particularly interested in opinions that have a particularly negative view of one or the other, so long as you explain why.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 2 years ago (1 children)

I mean as in renting out servers (VMs), where untrusted people have full root access.

[–] phase_change 1 points 2 years ago (1 children)

Ah. Yes, I have no plans to do something like that.

My answer still applies. If there’s a remote code exploit that can be used to gain root, running it in a container just gets you root there. Running it in a VM only gets you root there. Both provide layers to protect the underlying OS.

[–] [email protected] 2 points 2 years ago

Indeed, VMs are more secure than containers, but they come had a quite heavy price performance wise and are also harder to maintain. With Podman you can manage containers just like any other systemd service, which is really convenient.