Dokku seems like a good tool with good developper experience, equivalent to Heroku. It would allow you to quickly experiment. Want to setup a new web app / service ? Heroku-like simplicity, just some clicks and a git push.
Anyone who has tried dokku's postgres database solution ? Where to store state is IMO the big missing piece from these Paas tools. They solve the stateless compute part nicely (with Flynn you can even setup something Dokku-like on multiple servers with automatic failover) but there's nothing offering automatic failover for a database that doesn't require you to be a db admin.
I've been running it for a couple of years now, and it basically just works. Don't expect too much out of it, though: it's basically just a small but very convenient wrapper around Docker.
If you need replication, failover, automatic backups, scaling, or something of that order, Dokku is probably not what you're looking for. If you just have an app with a handful of users, it's absolutely amazing.
I looked into Flynn as well, but it seemed way too complicated for my use case: it's a bit overkill to spin up three machines when there's probably only one user at a time and it's idle all but 5 minutes a day.
Flynn can be run in single computer mode or any multiple of N+1. The issue with running single computer mode on Flynn is that if the Flynn core modules become unstable (most likely due to lack of RAM), you'll probably need to wait for self healing. In multi computer mode, you can basically kill 2 of the computers and still be functional.
Their standard mode prioritizes your apps over their management layer so if you happen to deploy an app that eats up all the RAM, expect to hard reboot that host in order to get the management layer back.
Right, but that's not a HA/continuous backup solution for the state (PostgreSQL db), so if the machine fails, you lose the database, and all the data since the last backup.
What I'd love is something Dokku-like in simplicity for setting up HA/master-slave postgreSQL. A tool that I just install on two servers and it does everything needed for HA such as replicate continuously.
Even without the HA, just continuous replication, this would be a great complement to Dokku.
I'm a heavy dokku user and I would love the same thing. Just simple replication to another machine in case of failure. A load balancer in front of them would be great for HA but I'd settle for manual fail-over as long as real-time data replication was as simple as dokku makes everything else.
Comments
Dokku seems like a good tool with good developper experience, equivalent to Heroku. It would allow you to quickly experiment. Want to setup a new web app / service ? Heroku-like simplicity, just some clicks and a git push.
Anyone who has tried dokku's postgres database solution ? Where to store state is IMO the big missing piece from these Paas tools. They solve the stateless compute part nicely (with Flynn you can even setup something Dokku-like on multiple servers with automatic failover) but there's nothing offering automatic failover for a database that doesn't require you to be a db admin.
I've been running it for a couple of years now, and it basically just works. Don't expect too much out of it, though: it's basically just a small but very convenient wrapper around Docker.
If you need replication, failover, automatic backups, scaling, or something of that order, Dokku is probably not what you're looking for. If you just have an app with a handful of users, it's absolutely amazing.
I looked into Flynn as well, but it seemed way too complicated for my use case: it's a bit overkill to spin up three machines when there's probably only one user at a time and it's idle all but 5 minutes a day.
Flynn can be run in single computer mode or any multiple of N+1. The issue with running single computer mode on Flynn is that if the Flynn core modules become unstable (most likely due to lack of RAM), you'll probably need to wait for self healing. In multi computer mode, you can basically kill 2 of the computers and still be functional.
Their standard mode prioritizes your apps over their management layer so if you happen to deploy an app that eats up all the RAM, expect to hard reboot that host in order to get the management layer back.
We've been running a Dokku instance on a single node with PostgreSQL on the same host without any issues for years. It's been pretty solid for us.
Right, but that's not a HA/continuous backup solution for the state (PostgreSQL db), so if the machine fails, you lose the database, and all the data since the last backup.
What I'd love is something Dokku-like in simplicity for setting up HA/master-slave postgreSQL. A tool that I just install on two servers and it does everything needed for HA such as replicate continuously.
Even without the HA, just continuous replication, this would be a great complement to Dokku.
I'm a heavy dokku user and I would love the same thing. Just simple replication to another machine in case of failure. A load balancer in front of them would be great for HA but I'd settle for manual fail-over as long as real-time data replication was as simple as dokku makes everything else.
Wouldn't that issue be the case for any DB host?