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.
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. 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.
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.
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.
This is a great opportunity to get HN's take on these tools: systems to streamline the management of containerized services deployed on self-managed hardware.
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?
Have tried almost every PaaS and same for me, I always come back to CapRover, it's the platform I've had the less issues with, it's simple and yet feature complete enough for me to run almost anything.
I'd love a better alternative if possible.
I struggle to grasp what it does. What's Vercel and what that does? Someone here in the comments mentioned coolify.io and Dokploy as more alternatives. None of those projects have a good description of what they do. They just "ship anything to anywhere". That's too broad, I need details, I need a short explanation of their basic mechanisms.
Vercel has been outdated for sometime and it is refreshing to see alternatives coming up. This one seems like superior to Vercel already, definitely worth the switch.
I like it but I always miss features or defaults like:
- internal network only with edge nodes (i.e tail scale out the box, + some edge nodes)
- option to deploy on multiple servers to scale with super simple non k8s approach.
I love devpu.sh and great that its getting traction
I had known about this project beforehand and here is something that i found interesting
I want to share more that they are written in htmx/python btw. This was the first time I saw somebody mention why on their reddit post in r/htmx and I actually saw that post out in the wild and It was a fun read and I might definitely try this out in the near future but I don't really know, I don't like UI's that much and I'd rather just deploy a container manually but their approach is really nice too and something that I want to try out in a hetzner vps one day for sure
Go star this repo or help them if you can! More the options the better (coolify,dockploy,devpu.sh) (to me personally devpu.sh seems the most minimalist with just python iirc)
This looks really slick, though it's a bummer that there isn't a quick way to try the hosted version. You mentioned the Vercel UX in the comments, and I think the single-click install on the hosted version is a significant part of it.
I like the idea of self-hostability, but not having to think about the deployment of the frontend piece has been a huge accelerant for me, someone who typically thinks only of ML and backend components.
Well, you're not forced to use the project, there's other similar alternatives without Python. Like it or not you've described 2 of the most popular languages on the planet, and being snarky towards someone building something for free isn't going to make anything better.
Everyone's listing their favorites in this space, so I'll list mine, Cosmos Cloud. Been solid so far for me. Even has no trouble with more complex docker compose-based applications like KASM workspaces (https://hub.docker.com/r/linuxserver/kasm / this does a docker inside docker sort of thing)
Pasting the website instead of the GitHub as the installation instructions are more up to date on the main site:
27 comments
[ 18.9 ms ] story [ 615 ms ] threadI 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.
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.
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?
Tiresome!
(I saw the comment re: Streamlined UX, but is there anything else?)
I had known about this project beforehand and here is something that i found interesting I want to share more that they are written in htmx/python btw. This was the first time I saw somebody mention why on their reddit post in r/htmx and I actually saw that post out in the wild and It was a fun read and I might definitely try this out in the near future but I don't really know, I don't like UI's that much and I'd rather just deploy a container manually but their approach is really nice too and something that I want to try out in a hetzner vps one day for sure
https://www.reddit.com/r/htmx/comments/1ne6ueo/devpush_a_ver...
Go star this repo or help them if you can! More the options the better (coolify,dockploy,devpu.sh) (to me personally devpu.sh seems the most minimalist with just python iirc)
EDIT: Just got approved for access - thanks!
[0] https://piku.github.io/
So now I'll have TWO clusterfucks of infested dependencies to deal with instead of just one.
Pasting the website instead of the GitHub as the installation instructions are more up to date on the main site:
https://cosmos-cloud.io/
No debs. Install: curl | sh.
facepalm-Picard.jpg
1. Is there a support for deploying into a multiple machines? If so, how does it work?
2. Where and how secrets are stored?
Working on that, you should soon be able to have a central /dev/push instance and remote nodes managed by it.
> 2. Where and how secrets are stored?
Environment variables are stored in the DB but encrypted using Fernet (https://github.com/hunvreus/devpush/blob/main/app/models.py).