Selfhosted

59897 readers

526 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:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam.
Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.
Don't duplicate the full text of your blog or git here. Just post the link for folks to click.
Submission headline should match the article title.
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

What else should I selfhost? (feddit.org)

submitted 4 months ago* (last edited 4 months ago) by cows_are_underrated@feddit.org to c/selfhosted@lemmy.world

69 comments fedilink hide all child comments

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 18 points 4 months 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.

[–] cows_are_underrated@feddit.org 2 points 4 months ago

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