this post was submitted on 14 May 2026
88 points (94.0% liked)

Selfhosted

61512 readers
1421 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:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

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

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

Do you have any advice or suggestions about it?

  • Hardware (what should be enough for a local PC, or VPS...)
  • Software (OS [Debian, Yunohost, other...], "containerization" (Docker, virtual machines?), dashboard, management, backups, VPN tunneling...)
  • "Utilities" to host (Lemmy, Peertube, Matrix, Mastodon, Actual Budget, Jellyfin, Forgejo, Invidious/Piped, local Pi-Hole, email, dedicated videogame servers like for Minecraft, SearXNG, personal file storage like Drive, AI [in the future, when I can afford a rig that can run a local model decently]...)

I'm aware it's a lot of stuff to take on, so, do you have any advice on where to start? (how to find a cheap PC to experiment with, if not get a VPS, what to test on it, what "utilities" to try self-hosting first...)

you are viewing a single comment's thread
view the rest of the comments
[–] irmadlad@lemmy.world 1 points 3 months ago

My first question would be, how familiar are you with the Linux cli? How much experience do you have with Docker containers? You are right, your list is quite extensive. and there is nothing wrong with goals, but I would caution to start small and slow. I would learn how to:

  • Drive the Linux bus fairly well. I'm using Ubuntu Jammy for my servers, but there are other options. NixOS seems popular.
  • Understand what reverse proxies are and how to deploy one. Caddy is pretty much dead simple with a small learning curve. There are many of them to choose from tho.
  • Learn about various security implementations. Security is paramount. Fail2ban is a good start, but I would also explore Crowdsec, Wazuh, etc.
  • Learn about Docker and how to set up Docker containers so that they are secure.
  • Instead of mass deploying apps and containers, choose one. Get to know it on a personal basis. The installation process, the security aspect, etc. Things are easier when there is only one container to mother hen. Then as your knowledge base grows, add another......and so on.
  • Document everything you do. Seriously. You can't write too many notes. When you've successfully deployed your first app while documenting, go back and clean up your notes and make them a part of your 3,2,1 back up policy. I can almost guarentee you that 6 months down the road, you won't be able to remember every command you typed in or what you've done. Documentation makes troubleshooting much easier.
  • Speaking of backups, you'll need a reliable way to make backups of your server. Borg seems to be quite popular, but there are others.
  • Have fun!