| ▲ | Onavo 3 hours ago | |
The docs seem to be non existent. Is the canine yaml documented? You want docs like this: https://coolify.io/docs/applications/ci-cd/github/setup-app https://coolify.io/docs/applications/build-packs/dockerfile https://coolify.io/docs/applications/build-packs/overview Plenty of screenshots and exact step by step instructions. Throwing an "example git repo" with no documentation won't get you any users. Put your shoes into that of a Heroku/Vercel user. DevOps is usually Somebody Else's Problem. They are not going to spend hours debugging kubernetes so if you want to sell them a PaaS built on Kubernetes, it has to be fool proof. Coolify is an excellent example, the underlying engineering is average at best (from a pure engineering point of view it's a very heavy app that suffers from frequent memory leaks, they have a new v5 rewrite but it's been stuck for 2 years) but the UI/UX has been polished very well. | ||
| ▲ | czhu12 3 hours ago | parent [-] | |
Yeah working through documentation still. The goal isn’t so much to replace coolify. Mostly born out of my last start up that ran a $20M business, 15 engineers, with about 300-1000qps at peak, with fairly complex query patterns. I think the single VPS model is just too hard to get working right at that scale. I think north flank / enterprise applications, would be a better comparison of what canine is trying to do, rather than coolify / indie hackers. The goal is not take away kubernetes, but to simplify it massively for 90% of use cases but still give full k8s api for any more advanced features | ||