this post was submitted on 02 Feb 2026
80 points (91.7% liked)

Selfhosted

55759 readers
410 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
 

So, I am soon going to finally set up my first home server. Exams are not that far away, I am motivated as shit, my first own domain is bought and I want to level up my sysadmin skills.

Currently my plans look like this:

  • Host Jellyfin
  • Host my own NAS
  • Some form of hosted musicstreaming integration with my local music
  • Automate Backups and push them on my server
  • make all of the above things available where ever I want using my own self hosted domain.
  • run my own dns

In the long term I also want to be able to host my own webapps, since I will soon start to develop one for someone.

Now I want to know what suggestions do you have, for stuff thats really cool and that I can selfhost.

Edit: thanks for all the replies. Definitely going to look into this.

you are viewing a single comment's thread
view the rest of the comments
[–] cecilkorik@lemmy.ca 16 points 1 day ago (1 children)

Before you even start, consider adopting an 'infrastructure as code' approach. It will make your life a lot easier in the future.

Start with any actual code: If you have any existing source code, get it under git version control immediately, then prioritize getting it into a git hub like forgejo to make your life easier in the future. Make a git repository for your infrastructure documentation, and record (and comment/document too if you're feeling ambitious) every command you run in a txt file or an md file or a script, and do that as religiously as you can while you're setting up all this self-hosted stuff. You may want to dig it up later to try and remember exactly what you did or in case stuff goes wrong and you need to back off and try again. It might seem pointless now, but a year from now, you'll thank me.

Especially prioritize getting your git stuff moved into a self-hosted forgejo if any of your stuff is hosted on the microsoft technoplague called github.

That's a very good idea, will definitely do that.