181–186 of 186 posts
I've been fascinated by how little developers know how to take a service they have, and make it accessible on something like their home network. It's honestly a shocker to me. There's so much knowledge about the stack that gets lost with these services.
I don't mean it as discouragement but, at least for me, I would choose Heroku or Netlify because I don't want to self host it. I want someone else to manage all those bits for me. It's good experience building the app though and good to have alternatives available.
Why are people so afraid to self-host? It's usually cheaper and runs better than the hosted services. Get a cheap dedicated server from Hetzner, and you can run all your services there. Servers tend to keep working (usually longer than those cloud services do).
Earlier quoted context omitted.
Hi, I build NextJs in standalone mode per docs and it works pretty well, we keep it running using pm2 but I want to migrate to systems service. I would say any NextJs should work but we run DollarDeploy ourselves using NextJs 14
$deploy looks cool, I ll take it for a spin!
Earlier quoted context omitted.
Thanks for the links. I didn't know about SwiftWave. I have a page with a comparison table of self-hosted PaaS on my site: https://dbohdan.com/self-hosted-paas . It only covers options that don't use Kubernetes. I have just added SwiftWave.
Thanks for adding this. The core problem of most of the PaaS is the dependency on Swarm (serious workload can't be run on swarm from my experience, disaster recovery too tough). Working towards building an orchestrator.
Earlier quoted context omitted.
Thanks for sharing this. I was thinking of giving it a try, but hearing that zero downtime deployments don't work is a deal breaker for me, which is sad because Coolify looks amazing otherwise. I do wonder though, why do we even need an alternative to Dokku when it seems to provide everything we need?
I had thought Dokku was only for a single host(?) From their docs: > Dokku is an extensible, open source Platform as a Service that runs on a single server of your choice. [0] But they have a "pro" version that mentions something about "servers," plural.[1] So maybe that's the difference between regular and pro? [0]: https://dokku.com/docs/getting-started/installation/ [1]: https://pro.dokku.com/
Earlier quoted context omitted.
It seems to be killing all remaining connections, as it just stops old container when new is deemed healthy. So not completely downtime by definition, is it?
It is only Docker Compose that has some limitations, but for all other types of applications it is currently zero downtime, but improvements are planned in this area.