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
It really is such a cool concept. The autism in me hates the name though because there's always a server. I wish it were called a "container-based service" or even just "containers" instead of serverless to be more direct. Perhaps even "web functions."
There's so much big talk about scale but really, scaling is not that important to 99% of businesses I've worked at. You're not a startup. Your typical server has a huge amount of resources if managed appropriately. I guarantee and would bet money that you'll never have a million users let alone a billion using your medical coding web app. Like, sit down!
Problem is containers mean OCI/Docker containers for most people, which distinctly are little OSs (the kernel is shared), where serverless creates a common OS stack and application framework as well.
Absolutely. People really sleep on just how much traffic a simple low end server running a PHP framework can handle. I've ran systems with a million users (combined across multiple domains and clients but still) and it was just fine with a single database server and a few web servers. They would have needed to hit the tens of millions of users before serious refactoring or rewriting would have ever been necessary to consider.