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'll rephrase it more clearly then. Selfhosting focuses on the hosting aspect of software. !programming@programming.dev focuses on the development aspect of software. This article talks about the architectural decision made during development. It doesn't talk about how to host serverless. It doesn't even talk about why you wouldn't want to selfhost serverless. It talks about bad software patterns the come with serverless. It also talks about the cost of running those things but even that is geared more towards enterprise level devops people.
It might be an interesting read from the software developer perspective but it's not interesting from the selfhoster perspective, because the article has nothing to do with selfhosting.