this post was submitted on 26 Jun 2023
15 points (100.0% liked)

Selfhosted

40324 readers
529 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 1 year ago
MODERATORS
 

Hey all,

Just wondering what the consensus is on hosting directly on a computer versus virtualization? Right now I'm hosting my Lemmy instance on a Hetzner VPS, but I would like to eventually migrate to my Linux box at home. It currently runs as a media PC (Ubuntu) in the living room, but I always intended to self-host other software on the side since it should be more than capable of doing both (Ryzen 5600G, 16gb DDR4).

I'm just torn though - should I host a virtual machine on it for Lemmy, or run it directly on Ubuntu as-is? I plan to do some further self-hosting projects as well later down the line.

you are viewing a single comment's thread
view the rest of the comments
[–] BrainTheBest5@lemm.ee -1 points 1 year ago

If you use a full VM you'll lose plenty of performance and I don't think it'll cope really well with domain names. If you really want to go the "keep everything separated" route use container software, like Docker. It'll use the same kernel as the host, so no weird networking rerouting/bridging etc.. I don't have any experience with containers, since I run all of my "homelab" bare metal on a Pi, and with this approach I never faced any issues. Containers could be useful if you were running something unorthodox like Gentoo and you need to run software that won't work on it, even if compiled to run, but it exist as a package on another distro. Then you can just spin up a container for that distro, install the software et voilà, you're ready to go. AFAIK there shouldn't be a package for lemmy on any distro, so just clone the source code and compile it, it should be fairly distro-agnostic. Maybe you could compile it in a container to keep your host clean of compile dependencies, but other than that, there's no real gain. I like to compile stuff, so having a shitload of dependencies already there is pretty handy for me, but for a production system, it's better to keep it clean.