11–20 of 102 posts
This looks very sleek but coolify.io is also open source and a more mature project in my opinion.
I built /dev/push because I wanted to offer a more streamlined UX, closer to what Vercel offer.
I am planning on adding more runtimes (there's a PR for Bun for example), support for custom containers and support for Docker Swarm, allowing you to manage multiple servers with a single instance.
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.
What's the difference with Dokploy ?
I wanted to build something closer to what Vercel offers, with a more streamlined UX out of the box.
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. Similarly, I maintain that if you don’t know how to administer and tune an RDBMS, you shouldn’t be using it for anything that matters.
If you think this sounds like gate-keeping, I’d ask you to re-read what I wrote. I think you have a responsibility to others who are relying on your skills to know what you’re doing, or at the very least, understand enough about their fundamentals to know how to reverse mistakes.
This looks very sleek but coolify.io is also open source and a more mature project in my opinion.
Coolify.io is definitely more mature. I built /dev/push because I wanted to offer a more streamlined UX, closer to what Vercel offer. I am planning on adding more runtimes (there's a PR for Bun for example), support for custom containers and support for Docker Swarm, allowing you to manage multiple servers with a single instance.
"Open source X alternatives" are dime-a-dozen and put a limit on what you can be in the eyes of users. It also sets expectations such that differences easily become disappointment. Not having a global CDN can otherwise simply be out of scope but can be "missing feature" when pitched as an alternative to an established service.
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…
I'm also working on adding manual steps so that folks who prefer to deploy the app themselves can do so.
I initially had the app deployed with Terraform + Ansible, but rewrote it as a bash script as I thought it'd be lower friction.
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.
Earlier quoted context omitted.
Coolify.io is definitely more mature. I built /dev/push because I wanted to offer a more streamlined UX, closer to what Vercel offer. I am planning on adding more runtimes (there's a PR for Bun for example), support for custom containers and support for Docker Swarm, allowing you to manage multiple servers with a single instance.
I think you can get stronger by building your own identity (rather than "like vercel") - starts with the headline/tagline and pitch in a way that stands on its own. "Open source X alternatives" are dime-a-dozen and put a limit on what you can be in the eyes of users. It also sets expectations such that differences easily become disappointment. Not having a global CDN can otherwise simply be out of scope but can be "m…
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.