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: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
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.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
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!
view the rest of the comments
I mainly just use bare SSH and/or point my web server to my repos as I don't really need a whole UI for stuff I'm pretty much the only one that will ever use it.
I feel like it's a git feature that's often overlook by those that have only used to GitHub/GitLab/Gitea before. Git was originally designed to just be a folder on a server you have SSH access (read-write) or HTTP(S) access (read-only).
I've used Gogs and Gitea in the past but found it overkill for my needs.
Exactly what I do. Unless you need fancier collaboration features--issue tracker, UI for handling PRs, etc--a bare repo on the other side of ssh plus something like cgit if you want to make the code available via a browser is perfectly sufficient.