If those are wrong expectations, you might consider changing your marketing.
See https://news.ycombinator.com/item?id=26581027 for recent discussion.
Also see: https://answers.netlify.com/t/support-guide-minimizing-impac... ("To make sure you can minimize the impact of our single-homed loadbalancer being down")
If one was using CNAME flattening, there was zero impact.
Pretty niche requirement I know, but the TTFB was insane as it was serving traffic from Brazil at that time.
This was around June 2020, if I recall so maybe things have changed. Moved to Cloudflare for our CDN
https://pbs.twimg.com/media/ExRnXpbWYAkOO-x?format=jpg&name=...
https://pbs.twimg.com/media/ExRnXpdXIAAmP_8?format=jpg&name=...
https://pbs.twimg.com/media/ExRnXpdXEAQHu5B?format=jpg&name=...
Though I'm sure many 3rd party ones exist for Dokku.
It's either that or it's the monster that is Kubernetes.
I absolutely want to be able to write small personal projects and have them deploy on my cheap server in a sensible way by simply pushing to my git repository.
At the moment I'm using caprover to do this, and it's so much better than doing it myself, but I think there's plenty of space to make this experience better.
But as others have pointed out, to call it a self-hostable Heroku & Netlify is indeed missing the point. It’s a bit of an oxymoron right?
The benefit of those services is in their CDN network, and the fact that they provide the platform and you don’t have to maintain your own server. Things I do not get with maintaining my own VPS.
Doesn’t mean I’m still not interested in this project, it looks pretty nice! But I would approach the marketing differently.
IMO you'd pay for Heroku because of the ability to have one vendor deal with your full stack, including Postgres, and having the ability to roll back / scale up with relative ease. You pay for that ease and support. (Everyone on the support team was a dev too)
For some teams it makes less sense than others. You can also probably find combinations of vendors to deal with most of the above.
Source: Was a customer architect there.
Definitely very cool and something to keep an eye on as it develops!
[0]: https://github.com/coollabsio/coolify/blob/main/api/packs/no...
Having deployment just be a push to a remote repository is really nice.
Will it be possible to use Golang? Or use the Dockerfile from the repository to build the container and run it? This way you can even compete with Portainer.
Private (ie. accessible to employees or contractors only) deployments of Coolify shouldn't trigger the requirement. I've seen some difference of opinion as to whether giving access to a supplier triggers the requirement, giving access to a client does generally require you to provide source to them.
Code merely deployed by Coolify should not be affected in any case.
So if you have a private network, but give a client/customer access to it, and they ask for the source, you will have the obligation to give it to them.
Assuming I'm running that on my NAS, I understand setting up port forwarding through my router; but what about domains and HTTPs?
That's essentially what I'm doing for my own website, as one example. Granted, that's on a VPS instead of a home NAS, but the idea's the same; neither a domain registrar nor an ACME provider necessarily care.
btw. I'm curious why their installer is 73MB in size: https://get.coollabs.io/coolify-installer
The massive popularity of things like cPanel shows that there is most definitely a market for people who want some assistance setting things up, but don't want to go down a fully managed route.
Thanks!
(edit: typo)
