this post was submitted on 31 Aug 2025
108 points (96.6% liked)

Selfhosted

51445 readers
585 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
 

I have been wanting to self-host recently I have an old laptop it's a Toshiba satellite m100-221 sitting around it only has 4gb of ram, but I don't know what is a good starting point for an OS for my home lab I discovered yunohost but heard mixed opinions about it when searching I would like lemmy's opinion on a good OS for a beginner wanting to start a home lab I would prefer a simple solution like yunohost but would like it to be configurable it's fine if it needs a bit of tinkering.

top 50 comments
sorted by: hot top controversial new old
[–] bjoern_tantau@swg-empire.de 46 points 2 weeks ago (3 children)

Without knowing what you actually want to do, I'd put Debian on it. Very good, very stable, very widespread OS with plenty of tutorials around for whatever you decide to do with it. Do a minimal installation and 4 GB RAM are plenty to play around with.

[–] fossilesque@mander.xyz 13 points 2 weeks ago (2 children)

I use debian for my ancient media server. It's great.

[–] adarza@lemmy.ca 7 points 2 weeks ago

i use dietpi, which is built upon a minimal debian.

[–] bjoern_tantau@swg-empire.de 4 points 2 weeks ago* (last edited 2 weeks ago)

Even better when you're already familiar with it. And I'd consider a media server to already be "selfhosting".

Edit: Sorry, thought you were OP.

[–] melroy@kbin.melroy.org 4 points 2 weeks ago

Yup Debian would also be my way of getting started.

[–] uranibaba@lemmy.world 2 points 2 weeks ago

I second Debian because of the amount of information out there.

[–] Kirk@startrek.website 21 points 2 weeks ago (1 children)

XKCD 2501 applies in this thread.

OP, get CasaOS or Yunohost. Very very simple. Your laptop is fine (you'll probably want to upgrade the ram soon).

[–] darkan15@lemmy.world 7 points 2 weeks ago (2 children)

XKCD 2501 applies in this thread.

I agree, there are so many layers of complexity in self-hosting, that most of us tend to forget, when the most basic thing would be a simple bare metal OS and Docker

you'll probably want to upgrade the ram soon

His hardware has a max ram limit of 4, so the only probable upgrade he could do is a SATA SSD, even so I'm running around 15 docker containers on similar specs so as a starting point is totally fine.

[–] BuboScandiacus@mander.xyz 5 points 2 weeks ago (1 children)

simple bare metal OS and Docker

That’s exactly what the XKCD is about, what you wrote is just like the chemical formulas they are talking about in the comic for your average person

[–] Lumisal@lemmy.world 2 points 2 weeks ago (1 children)

Agreed.

I've been using Linux for years.

I've done minor coding.

I've even installed Adguard and a VPN on a router.

Built my own water cooled PC.

I still don't quite understand what Docker is or does, or containerized stuff. I've avoided most networking stuff since XP, and it's basically a completely other field of tech as far as I'm concerned, like Math is to Physics.

[–] Korhaka@sopuli.xyz 1 points 1 week ago

I use VMs instead. I understand those and can pretend the benefits matter.

[–] Korhaka@sopuli.xyz 1 points 1 week ago (1 children)

Surely most basic is an old computer and double clicking minecraft_server.jar? Pretty sure that is the first server I ran for people outside of my LAN actually.

load more comments (1 replies)
[–] dihutenosa@piefed.social 18 points 2 weeks ago (2 children)

Step 1: be psychologically prepared to break it all. Don't depend on your services, at first, and don't host stuff for others, for the same reason.

Yunohost? Good for trying out stuff, I suppose. I haven't tried it myself. You could also try Debian, Alpine, or any other. They're approximately equivalent. Any differences between distros will be minuscule compared to differences between software packages (Debian is much more similar to Alpine than Nextcloud to Syncthing).

4GB of RAM? Don't set up a graphical interface. You don't need a desktop environment to run a server. Connect to it via SSh from your regular PC or phone. Set up pubkey auth and then disable password auth.

I recommend setting up SSH login first, then a webserver serving up HTTP, only, accessible via IP address.

Next comes DNS - get a name at https://freedns.afraid.org/

Then add HTTPS, get the certs from LetsEncrypt.

Finally, Nextcloud. It runs kind of "inside" your webserver. Now you can back up your phone, and share photos with family, etc.

[–] Lumisal@lemmy.world 2 points 2 weeks ago (1 children)

asks for help starting with new tech stuff for the first time

Comment that tells them to not use a GUI has 20 upvotes so far

This is why it won't be the year of Linux anytime soon. Basically sending someone new straight into the deep end.

[–] dihutenosa@piefed.social 2 points 1 week ago

Eh, OP says:

I am familiar with Linux and comfortable in terminal

... and is constrained by little RAM. My stance stands.

load more comments (1 replies)
[–] melroy@kbin.melroy.org 14 points 2 weeks ago

Nobody is saying it, so I will. The most important thing is to just get started!

It doesn't matter if you go for a plain Debian server or a fancy proxmox installation with high availability. I believe the most important thing is just to start and experiment. And enjoy!

[–] uranibaba@lemmy.world 9 points 2 weeks ago (3 children)
  1. Figure out what you want to host.
  2. Read up on what is required to host that.
  3. Understand what is required to host that.
  4. Skip step 3, wing it and search the internet as you go.
[–] Appoxo@lemmy.dbzer0.com 1 points 1 week ago (1 children)

Essentially what I did to some degree.

[–] uranibaba@lemmy.world 2 points 1 week ago* (last edited 1 week ago)

Same here. I remember playing minecraft and wanted to install some mod on my server. There were instructions and I followed them. Problems? Search the web.

I also tried to run TeamSpeak on an RPI at some point, and that was when I learned about ARM.

load more comments (2 replies)
[–] drkt@scribe.disroot.org 7 points 2 weeks ago (1 children)

Take a few steps back and ask yourself what needs you're trying to fill. I never heard of Yunohost before, but it sounds high-level and abstract. Are you a programmer? Are you familiar with Linux? Are you comfortable in a terminal? Are you familiar with networking?

Find out what you want to do before installing "everything and the kitchen sink" solutions.

[–] artiman@piefed.social 3 points 2 weeks ago* (last edited 2 weeks ago) (2 children)

I am familiar with Linux and comfortable in terminal, but I am not comfortable networking, and I am not a programmer.

[–] drkt@scribe.disroot.org 3 points 2 weeks ago (7 children)

So what do you want to do? What need are you trying to fill?

load more comments (7 replies)
[–] brewery@feddit.uk 2 points 2 weeks ago

If you're comfortable in the terminal you'll be fine just starting out and figuring it as you go. Be ready for a few reinstalls but it becomes part of the fun, albeit sometimes frustrating! Go for a mainstream server os like Ubuntu or Debian (as if you google them with any issue you're likely to find at answer). Get SSH up and running with keys for security, install tailscale and don't expose to the internet until you feel more comfortable. Install docker then start on one software you think will be useful, get it up and running then move onto the next. I would recommend homepage as a front end then keep it up to date with new software so you can quickly see what you have and what ports are in use. Vaultwarden is useful for the admin passwords. I use authentik for sso but would try caddy if I was starting now.

[–] cecilkorik@lemmy.ca 5 points 2 weeks ago (1 children)

I'll add a vote to all the people suggesting Yunohost. Yunohost is a perfect place to get your feet wet with basically no experience required. I've played with it myself and it does a good job of simplifying and holding your hand without oversimplifying or keeping you on a strict, tight leash. It even helps you deal with common newbie issues like dynamic IPs so you can become more reliably available on the internet, something that a lot of other guides just assume you're going to have a static IP assigned by your ISP or VPS and handwave away the complexity of what you'll have to do if you have a dynamic IP like most home connections. (Experienced self-hosters gradually discover that having access to a static IP somewhere, anywhere, makes life a lot easier, but don't worry, you'll get there too eventually, it's not important when getting started)

You can get started by working your way through the process here.

[–] 3dcadmin@lemmy.relayeasy.com 3 points 2 weeks ago

I agree but I do have to say that Yunohost is becoming bloated. Successive versions run way slower than they used to - I know it is part of the security and ease of use but it is becoming noticeable. You can also use some docker things in yunohost but for an absolute beginner Yunohost is by far the best way to do it.

[–] adarza@lemmy.ca 4 points 2 weeks ago (1 children)

don't expect a 19 year old laptop to perform all the tricks something more 'modern' can do, such as transcoding video for a streaming media server. also note that a t5600 is not a ulv chip (draws as much as 34w under load, on its own)--so probably not a candidate to run 'lid down' without some outside help for cooling.

it's not fast, it's not power efficient, it has slow networking (10/100 and 22-year old 'g' wifi), and lacks usb3 for 'tolerable' speed on extra external storage space---but it will be 'ok enough' for learning on.

if you go with something like yunohost or even dietpi, you will pretty much restrict yourself to what it can run and do and how it does it. if you want more 'control' or to install things they don't offer themselves, you'll need to 'roll your own'. a base (console only) debian would be a great place to start. popular, stable, and tons of online resources and tutorials.

load more comments (1 replies)
[–] billwashere@lemmy.world 3 points 2 weeks ago (1 children)

Start with docker. Any OS will do. Most Linux distros are better but I run docker on Mac, Linux, Windows (not a lot in windows since I despise Microsoft but it does work).

The great thing about docker is it is very portable, modular, and easy to get back to a known state. Say you screw something up, just revert and start over. It’s also very easy to understand in my opinion. It’s like all the benefits of virtualization with much less over head.

[–] mic_check_one_two@lemmy.dbzer0.com 1 points 2 weeks ago* (last edited 2 weeks ago) (1 children)

Yeah, my only note is that Docker on Windows is… Kinda fucky? It uses WSL to run Linux in the background, which means that the volumes it creates aren’t easily accessible by Windows. If your container requires editing a config.json, for instance… That can be daunting for a newbie on Windows, because they won’t even know how to find the file.

You can work around this by mounting your volumes directly to a C:\ folder instead, but that’s something that many tutorials just completely skip past because they assume you already know that.

[–] billwashere@lemmy.world 4 points 2 weeks ago (1 children)

I’ve never understood the reason for WSL. If you want Linux, run Linux. At the very least in a VM.

load more comments (1 replies)
[–] MangoPenguin@lemmy.blahaj.zone 2 points 2 weeks ago

Install Debian as a server with no GUI, install docker on it and start playing around.

You can use Komodo or Portainer if you want a webUI to manage containers easily.

If you put any important data on it, set up backups first, follow the 3-2-1 rule by having at least 2 backups in place.

The problem with stuff like yunohost is when it breaks you have no idea how to fix it, because it hides everything in the background.

Hosting isn't OS specific, and in my experience its more about docker. But as far OS goes, I'd say Debian or Ubuntu with the intent of moving onto something like Proxmox

[–] baduhai@sopuli.xyz 2 points 2 weeks ago

So, it might not sound like much, but 4gb of ram is plenty enough to do quite a bit with self hosting.

If you want to self host, and use it as an opportunity to learn, I recommend you install Debian, and get your hands dirty. If just want to self host without much of a headache, yunohost seems cool, but I've never used it, so I can't recommend it.

[–] Botzo@lemmy.world 2 points 2 weeks ago

I might recommend starting with a project.

Something like getting pi-hole running. This would help you learn some of the networking basics. But I'd recommend reading at least enough to have a conceptual foundation about the things you don't understand along the way (DNS, DHCP, etc).

You'll want one of their supported OS choices to keep things simple. That means one of: fedora, debian, ubuntu, or centos. I might steer you away from centos just because its user base is a bit more linux-pro so finding specific help might be more daunting, but I don't have much experience with it either. Maybe use a "server" variant to keep your system demand to a minimum (boot to terminal only).

[–] downhomechunk@midwest.social 2 points 2 weeks ago (1 children)

Step 1: Install proxmox

Step 2: run the post install script here, disable anything enterprise, test or related to high availability.

Step 3: check out the other scripts on the link. I suggest starting with a pi hole and experimenting from there.

https://community-scripts.github.io/ProxmoxVE/

[–] sugar_in_your_tea@sh.itjust.works 1 points 2 weeks ago (3 children)

That sounds overly complicated, why get VMs involved? Just install Debian or something and get things working.

Proxmox is good if you know you want multiple VMs running for specialized needs. But multiple VMs isn't happening on 4GB RAM.

[–] Windex007@lemmy.world 3 points 2 weeks ago (7 children)

Easily can have multiple LXCs, and being able to take snapshots for backup is probably a nice thing to have if you're just learning.

And if they get more hardware, moving VMs to other clustered proxmox instances is a snap.

load more comments (7 replies)
load more comments (2 replies)
[–] darkan15@lemmy.world 2 points 2 weeks ago* (last edited 2 weeks ago) (1 children)

I have a Dell Inspiron 1545, that has similar specs to yours running Debian with Docker and around 15 services in containers, so my recommendation would be to run Debian server (with no DE), install docker, and start from there.

I would not recommend proxmox or virtual machines to a newbie, and would instead recommend running stuff on a bare metal installation of Debian.

There are a bunch of alternatives to manage and ease the management of apps you could choose from like, yunohost, casaOS, Yacht, Cosmos Cloud, Infinite OS, cockpit, etc. that you can check out and use on top of Debian if you prefer, but I would still recommend spending time on learning how to do stuff yourself directly with Docker (using docker compose files), and you can use something like Portainer or Dockge to help you manage your containers.

My last recommendation would be that when you are testing and trying stuff, don't put your only copy of important data on the server, in case something break you will lose it. Invest time on learning how to properly backup/sync/restore your data so you have a safety net in case that something happens, you have a way to recover.

[–] bradbeattie@lemmy.ca 2 points 2 weeks ago (1 children)

As a counterpoint to no proxmox, I get a lot of utility in being able to entirely destroy and reprovision VMs. I get it adds a layer of complexity, but it's not without its merits!

[–] darkan15@lemmy.world 2 points 2 weeks ago* (last edited 2 weeks ago) (1 children)

I get your point, and know it has its merits, I would actually recommend Proxmox for a later stage when you are familiar with handling the basics of a server, and also if you have hardware that can properly handle virtualization, for OP that has a machine that is fairly old and low specs, and also is a newbie, I think fewer layers of complexity would be a better starting point to not be overwhelmed and just quit, and then in the future they can build on top of that.

[–] bradbeattie@lemmy.ca 2 points 2 weeks ago

No disagree here. :)

[–] oeuf@slrpnk.net 2 points 2 weeks ago

I've been using YUNOhost for the last 3 years and it's been great. I had no prior experience and would have had no chance of self-hosting without it.

[–] Damage@feddit.it 1 points 2 weeks ago

RAM is a bit limiting, but OpenMediaVault is a NAS OS with a serviceable docker interface.

load more comments
view more: next ›