Would love to pick your brain as to what our quirks are and how we might avoid them in the future. Feel free to hit up the `@dokku` twitter account, catch us on the gliderlabs slack (https://glider-slackin.herokuapp.com), or even provide feedback in the Discussions section of the primary Github repository (https://github.com/dokku/dokku/discussions).
@josegonzalez, thanks so much for all of your work on Dokku and for being so responsive in the community for the last couple years. We tried Flynn at one point and had enough issues we moved back to dokku within 2 months and have been happily living on it for years now. You helped me directly with an issue with DB naming at one point, much appreciated!
Going to take you up on this offer. We've been running Dokku in production for years; and have a few quirks which have resulted in us evaluating moving to k8s.
Assuming you’re a company (as opposed to an individual), if you want a PAAS, there are a few different options that in my view are sustainable which I think is the key criteria for adopting something for your platform.
- Heroku. Sure it’s a bit expensive but it’s still super easy if you’re a dev.
- OpenShift. If you’re a really big enterprise, OpenShift is a reasonable choice for PAAS. But only if you’re huge.
- Kubernetes. Yes, it’s complicated. Yes, it has a steep learning curve. But it’s open source, has a huge and growing ecosystem, and it has less lock in than any other PAAS-like thing that I can think of.
The main downside of Kubernetes beyond its complexity is that you still have to build abstractions on top of it for your developers. But that world is improving regularly.
I went through this evaluation process again recently for an open source project for a client and came to the conclusion that, for small projects, Heroku provides immense value. Given the features and free-tier add-ons it’s definitely worth the 7p/m and I don’t know if I would class it as expensive anymore when taking all it’s features into consideration. I’d like to see http2 support though.
Watching and waiting for https://render.com to mature a little as it seems slightly better value.
Yes, I'm a huge fan of Convox [1]. One thing that don't make very clear is that the paid "Convox Pro" hosted console is optional, and convox/rack [2] is completely free and open source. You can set everything up with a single command, and then interact with your rack and app directly through the CLI. I really like how simple and opinionated it is, even though their new v3 version uses Kubernetes behind the scenes.
