this post was submitted on 31 Mar 2026
232 points (96.8% liked)

Selfhosted

56953 readers
868 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.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

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

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

Any recommendations for my Homepage setup or services to add/replace?

you are viewing a single comment's thread
view the rest of the comments
[–] krashmo@lemmy.world 2 points 6 hours ago (1 children)

Look into docker containers in general. If I was going to start from scratch in your position this is what I'd do:

Install a Linux distribution on the computer you plan to use for self hosting. I found Debian with the KDE plasma desktop environment to be pretty familiar coming from Windows. You could technically do most of this on Windows but imo self hosting is pretty much the only thing that a casual user would find better supported through Linux than Windows. The tools are made for people who want to do things themselves and those kinds of people tend to use Linux.

Once you have a Linux distribution installed, get docker set up. Once docker is set up, install portainer as your first docker container. The steps above require some command line work, which may or may not be intimidating for you, but once you have portainer functional you will have a GUI for docker that is easier to use than CLI for most people.

From this point you can find the docker installation instructions for any service you want to run. Docker containers have all the required dependencies of a given service packaged together nicely so deploying new services is super easy once you get the hang of it. You basically just have to define where the container should store it's data and what web port you want to access the service on. The rest is preconfigured for you by the people who created the container.

There's certainly more to be said on this topic, some of which you would likely want to look into before you deploy something your whole family will be using (storage setup and backup capability, virtual machines to segregate services, remote accessibility, security, etc). However, the above is really all you need to get to the point where you can deploy pretty much anything you'd like on your local network. The rest is more about best practices and saving yourself headaches when something breaks than it is about functionality.

[–] quick_snail@feddit.nl 1 points 6 hours ago (1 children)

Dont do this. OP built a security nightmare

[–] irmadlad@lemmy.world 1 points 4 hours ago (1 children)

OP built a security nightmare

How so?

[–] quick_snail@feddit.nl 1 points 2 hours ago (2 children)

Docker will happily download malicious containers. It doesn't use cryptography to verify what it downloads during the layer pull.

[–] krashmo@lemmy.world 2 points 2 hours ago

That's overly dramatic phrasing and you know it. Adding this kind of hyper technical quip to a thread aimed at beginners is insane. Stop doing that.

[–] irmadlad@lemmy.world 1 points 2 hours ago

Linux can do that too from miners, backdoors/SSH credential stealers, bots, rare ransomware but they exist, rootkits, spyware, and supply‑chain attacks