@jikkujose@flavorjones@palkan_tula@inazarova@dhh@jasonfried Because it's SQLite?, I don't know. Single-writer is a limitation, but I don't think it's realistic to hit for in a normal self-hosted use case.
I did a new load test with 2GB/1CPU, and the results are exceptionally good.
https://t.co/MQ18vCVMoV
Introducing Sabha, an open-source alternative to Slack and Discord for chat based communities.
Your brand.
Your domain.
Your data.
Fully self-hosted.
Create a community in 30 seconds ⬇️ 🧵
I have always felt it is absurd that everyone defaults to Discord as a place for chat community, even in case open-source projects.
Why not self-host?
Every alternative has become a VC-funded enterprise tool attempting to replace Slack, resulting in a complex tech stack that makes self-hosting on a small server impractical.
Using SQLite as a database and making it multi-tenant means that each community has a separate database file. That dramatically simplifies the stack.
You can host it on a basic $5 VPS on Hetzner. I wanted such a solution to exist, so I gave it a try.
Checkout repo for selfhosting guide:
https://t.co/f5iiKZru1s
@flavorjones@palkan_tula@inazarova@dhh@jasonfried Campfire did the basics right, Sabha completes the feature set.
You cant try out Campfire without self-hosting. Sabha fixed it with multi-tenancy. You can start with https://t.co/el5VONTonp and migrate to a self-hosted instance under your domain whenever you like.