4 ms·
Heya, Disco is the open source PaaS I've been working on with my friend Antoine Leclair. Lots of conversation & discussion about self-hosting / cloud exits the
by gregsadetsky 1y ago
Heya, Disco is the open source PaaS I've been working on with my friend Antoine Leclair.
Lots of conversation & discussion about self-hosting / cloud exits these days (pros, cons, etc.) Happy to engage :-)
Cheers!
- bstsb 1y agowhat does this service offer over an established tool like Coolify? currently hosting most of my services on a cheap Hetzner VPS so i'm interested what Disco has to offer
- odie5533 1y agoThere's quite a few now. Coolify, Dokku, CapRover, Kamal.
- ajayvk 1y agohttps://devpu.sh/ https://devpu.sh/ is another alternative, it has a nice UI built with Hypermedia (HTMX). I am building https://github.com/openrundev/openrun/ https://github.com/openrundev/openrun/. Main difference is that OpenRun has a declarative interface, no need for manual CLI commands or UI operations to manage apps. Another difference is that OpenRun is implemented as a proxy, it does not depend on Traefik/Nginx etc. This allows OpenRun to implement features like scaling down to zero, RBAC access control for app access, audit logs etc. Downside with OpenRun is that is does not plan to support deploying pre-packaged apps, no Docker compose support. Streamlit/Gradio/FastHTML/Shiny/NiceGUI apps for teams are the target use case. Coolify has the best support and catalog of pre-packaged apps.
- alberth 1y agoOr Dokku, Dokploy or CapRover Would be great to have a comparison on the main page of Disco
- gregsadetsky 1y agoCoolify and other self-hosting options such as Kamal are great. We're all in the same boat! I'd say the main differences is that we 1) we offer a more streamlined CLI and UI rather than offering extensive app/installation options 2) have an api-key based system that lets team members collaborate without having to manage ssh access/keys. Generally speaking, I'd say our approach and tooling/UX tends to be more functional/pragmatic (like Heroku) than one with every possible option.
- Onavo 1y agoThere's also Canine and Kubero https://news.ycombinator.com/item?id=44292103 https://news.ycombinator.com/item?id=44292103 https://news.ycombinator.com/item?id=44873057 https://news.ycombinator.com/item?id=44873057
- JrProgrammer 1y agoThere is also Dokploy which is what I've been using on my homelab for a while. https://dokploy.com/ https://dokploy.com/
- deleted 1y ago[deleted]
- martinald 1y agoJust to be aware when you say "Even with all 6 environments and other projects running, the server's resource usage remained low. The average CPU load stayed under 10%, and memory usage sat at just ~14 GB of the available 32 GB." The load average in htop is actually per CPU core. So if you have 8 CPU cores like in your screenshot, a load average of 0.1 is actually 1.25% (10% / 8) of total CPU capacity - even better :). Cool blog! I've been having so much success with this type of pattern!
- gregsadetsky 1y agoSharp eye! Thanks. Fixed
- __mharrison__ 1y agoThanks for sharing. I have an app I'm working on and this seems perfect for it.
- carzilla 1y agoHi, Interesting project. Do you have any screenshots of the UI of Disco?
- gregsadetsky 1y agoThe microscopic screenshot on the homepage of https://disco.cloud https://disco.cloud is almost everything we have - I really really need to update the docs Oh, there’s actually this tutorial that shows a tiny preview of it: https://disco.cloud/docs/deployment-guides/meilisearch https://disco.cloud/docs/deployment-guides/meilisearch Thanks for the reminder!