Our great sponsors
-
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
Fly CDN
Discontinued A set of useful libraries for Edge Apps. Run locally, write tests, and integrate it into your deployment process. Move fast and maybe don't break things? Because, gosh darnit, you're an adult. (by superfly)
-
-
swarmlet
Discontinued A self-hosted, open-source Platform as a Service that enables easy swarm deployments, load balancing, automatic SSL, metrics, analytics and more.
-
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
-
Aside from having an admin UI, would you be willing to talk a bit about how caprover is easier to use than dokku?
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).
(I am the dokku maintainer).
As others have mentioned, the current site (README.md) says very little about what Flynn is.
You can see a version of the repo and README.md, just before it became unmaintained, here:
https://github.com/flynn/flynn/tree/2c20757de8b32a40ba06f7e5...
IMHO it would have been much better if the maintainers had added the "Flynn is Unmaintained" information to the top of the README.md rather than removing all the existing information. I'll submit a GitHub issue suggesting it.
A plea to project maintainers in general: Please include enough information in your top-level README (or README.md, or README.whatever) so that someone who has never heard of your project can find get a good overview. I've also seen READMEs that only discuss the most recent changes. That's fine for readers who have already been following the project, but not for a more general audience.
I was definitely a _very_ late adopter of the program, but because it was so badly documented and seemingly dead even a few months ago I dropped it as well.
I use https://fly.io now for this purpose. It's not self-hosted, but it does the job for me :)
Qovery is partially open source and have a 100% free plan for individual developers. https://www.qovery.com
I'm working on a self-hosted, open source PaaS called Swarmlet. I really like Dokku, but I needed something that's a bit more scalable to my needs.
The installer is currently broken, I simply don't have enough time / bandwidth right now to work on it unfortunately.
That said, if you want to contribute, please let me know! I hope to get things running again soon.
https://swarmlet.dev or https://github.com/swarmlet/swarmlet
Sad news, but I'm not surprised with this. The complete ecosystem was "killed" (if that can be said) with K8s buzz and hipsterism (sorry guys, but I see K8s as Hadoop/BigData of modern days - a solution from a huge company that has no place in 90% setups). Alternatives like Deis [2] moved to K8s a long time ago. My favorite tool for some time, Rancher [3], did that as well.
I've been using Dokku [1] for a few years on a small setup, surprisingly without a single problem, taking into account it was written in "not-so-cool" bash. And I was considering Flynn as the next step if I need to scale it because Dokku doesn't have clustering support (added: looks like clustering support for Dokku is in work [4]).
After many checks, I got the impression Flynn simply wasn't there yet. Either because of low development pace, low number of supported appliances, or something else, I'm not sure. In the end, I picked up Ansible for more distributed setups.
[1] https://dokku.com/
[2] https://deislabs.io/
[3] https://rancher.com/
[4] https://www.reddit.com/r/devops/comments/bgpw5w/flynn_vs_dok...
[2]: https://github.com/dokku/dokku-scheduler-kubernetes
Hi everyone, I'm one of the maintainers of Porter (https://github.com/porter-dev/porter). We are building a Kubernetes-powered PaaS that runs in your own cloud. We consider Porter to be the next-gen successor to Flynn in the era of k8s.
We had the pleasure of getting on a call with the Flynn founders last week and learned so much from their experience. It was incredible to hear the first-hand account of the past 7 years building Flynn (seriously, what a ride). We took their lessons and advice to heart and hope to fill the void Flynn is leaving behind.
To the founders of Flynn and all contributors, thanks so much for building such an awesome project and paving the way. Porter is still in its early stage, and we're super excited to start sharing our progress with the community. Exciting stuff coming your way soon - stay tuned!
Yes, I'm a huge fan of Convox [1]. One thing that don't make very clear is that the "Convox Pro" hosted console is optional, and convox/rack [2] is completely free and open source.
I'm sad to see that Convox still isn't getting the recognition it deserves, because it really is like having Heroku in your own AWS account.
[1] https://convox.com
[2] https://github.com/convox/rack