Selfhosted
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.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
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.
-
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:
- 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!
view the rest of the comments



Thanks yea I've used Codeberg before, but the main reason I use GitHub, is I try to create a good looking profile to point potential new Clients to when I'm looking for a new job, explaining Codeberg to them I feel is a step too much, and my income is Priority Nr1.
I'll fight the Open-Source, anti-Big-Tech fight elsewhere.
I totally get that
Quick heads up - codeberg has an option to auto push changes to github, or the other way around with a github action (I prefer codeberg first)
May want to give it a try, from a client perspective you can also use that to note that a distributed approach provides resiliency (and now it becomes a selling point too)
Nice thanks, that sounds good. I'd definitely only want to push to one place, if it then syncs to GitHub that's fine.
I'm with you, I don't like having to do the same thing more than once
I set up an "about my repos" repo, which has a readme detailing the process, and explanations of what is where and what they are all for, which is what I point clients to. That also has a link to my personal forgejo to demo local git as well (which can also sync, btw) along with a note that it may be down for various reasons like updates or changes I'm making, which is why I also sync elsewhere.
Depending on what services you're selling to clients, it makes for a neat and simple addition to the list of skills to demo!
And you're kind of making me want to use a mini rack as an excuse to my wife for a 3d printer, but she already knows I'm not getting rid of my 12-15RU racks under my desks, so I'm going to have to wait until we find the property we want so I can build my workshop....
Nice thanks!! You can get a 3D printer for fairly cheap to get started, the one I have is only 280 Euro now with 4 spools of filament
It seems that using multiple remotes is also possible. So instead of syncing two repos, push to both at once.
https://git-scm.com/docs/git-remote#Documentation/git-remote.txt-set-url
https://stackoverflow.com/questions/849308/how-can-i-pull-push-from-multiple-remote-locations/12795747#12795747
You can, but you can also run into some issues if you have git LFS, if one rejects for whatever reason, or sometimes just branch issues.
Thats why I prefer to go to one repo and push out from there, but it is absolutely doable with git by itself.