21–30 of 102 posts
Looks very comfy, I am glad there is so many new alternatives to manage deployments a la Heroku. I remember even back in 2018 it was hard to find any good options to beat Heroku's level of functionality. I made a Dokku wrapper myself and manage my deployments that way, I'm pretty happy about it these days, but again it's nice to see more alternatives in the wild.
Did you open source it?
I get the appeal, but am also horrified at the “let’s pipe scripts to bash with sudo,” and the lack of visibility into what the DB is doing. I am a huge proponent of running your own, but along with that comes a responsibility to know what you’re doing. If you don’t know how to harden a Linux box on your own, frankly you have no business hosting anything on it. Spin up a VM and learn from your mistakes first. Similar…
Vercel alternatives are getting traction and relevance after Vercel and CEO controversies like last weeks https://news.ycombinator.com/item?id=45416353
As such there are plenty of deployments, where the only deployment option is between Vercel, Netlify and co, usually Vercel ends up winning on the portfolio and partner deals.
You don't see geeks selling their Apple gear in droves, despite the deals that its CEO has been doing as well.
If you're self hosting, IMO following Vercel is not the model. Use KEDA and K8s, and if you need compute at the edge lean into Cloudflare. That way you're staying standardized, and your vendor lock in is for best in class edge support.
I get the appeal, but personally I stay away from k8s. I don't mind putting in work to set up my deployment pipeline, but on a day to day I just want to push code to my repo and potentially edit environment variables. That's the sweet spot I was trying to hit.
Earlier quoted context omitted.
I get the appeal, but personally I stay away from k8s. I don't mind putting in work to set up my deployment pipeline, but on a day to day I just want to push code to my repo and potentially edit environment variables. That's the sweet spot I was trying to hit.
you can do that with k8s and argo?
We've been running both CapRover and Coolify for a couple years. We quite like renting real dedicated servers (Hetzner, OVH), it is so much cheaper than the cloud and a minor management burden. These tools make it easy to bridge the gap and treat these physical servers like PaaS.
We have dozens of apps and services deployed on a couple large-ish servers with backups. Most modern back-ends do so little computationally and lots of containers can comfortably live together. 128GB of RAM and 64 cores can go a long way and surprisingly cheap in Hetzner, and having that fixed monthly cost removes a mental burden. It is cheap, simple and availability issues are so much rarer than people expect, maybe a couple mishaps a year that are easy to recover from and don't really have a meaningful impact for a startup.
Coolify feels more complete and mature, but frankly, after using both a lot, we now steer more towards the simplicity of CapRover. I see that Dokploy is also a major alternative to Coolify, don't know much about it.
How does /dev/push compare? Do you have any other recommendations in this vein? Or differing opinions on the tools I mentioned?
What I actually miss in Vercel is the lack of exposure to the underlying AWS Lambda infrastructure, at very least similar set of languages should be supported.
Vercel alternatives are getting traction and relevance after Vercel and CEO controversies like last weeks https://news.ycombinator.com/item?id=45416353
Vercel is like other big corporations that places like HN and Reddit like to hate, most C suites signing off consulting contracts and partner deals couldn't care less. As such there are plenty of deployments, where the only deployment option is between Vercel, Netlify and co, usually Vercel ends up winning on the portfolio and partner deals. You don't see geeks selling their Apple gear in droves, despite the deals th…
Earlier quoted context omitted.
I get the appeal, but personally I stay away from k8s. I don't mind putting in work to set up my deployment pipeline, but on a day to day I just want to push code to my repo and potentially edit environment variables. That's the sweet spot I was trying to hit.
Not trying to be dismissive here but if you're deploying regularly and you have plans to scale anything putting the time into learn and automate K8s pays off very quickly. What you're doing here gives me ORM vibes - good for training wheels and helping people that don't know stuff to be productive quickly, but ultimately a source of lots of problems that you wouldn't encounter if you didn't invest in a leaky abstract…