Flynn VS kubernetes

Considering other orchestration tools like dokku, dcos, deis, flynn, docker swarm, etc.. Kubernetes is no where near to them in terms of lines of code, on an average those tools are around 100k-200k lines of code.

> we are indeed writing a new orchestration system in Go, called `flyd`.

I know it's just a wild coincidence, but I couldn't help but be reminded of https://github.com/flynn/flynn

I love these projects and I'll definitely look into it more later. At the same time, I think it would be hard for me to want to leave Kubernetes. K8s isn't something that I love, but it's something that I know works and will continue to be supported in some fashion. I've seen Flynn (https://github.com/flynn/flynn) EOL. I've seen Docker Swarm's future be a bit hazy. I've seen Porter decide to put pretty restrictive limits on their free tier (though it is open source). I've seen Dokku lose steam and then pick up again - but still not be a solution for more than one server.

I love the idea of something that will Just Work, but a lot of stuff doesn't handle the parts I care about the most. Will my one-click PostgreSQL have a couple replicas in my cluster? Will it launch pg-backrest so I can have it backed up to S3? Will it deal with secret storage so I can just add my secrets in the UI and then have my apps grab those secrets as environment vars? Will it fail-over nicely?

Coolify looks really cool and I do want to check it out for real later (probably over the weekend to be realistic). However, it seems like it's single-server (for now) and that seems less compelling for me at the moment. It looks like you're planning on K8s support which would just be wonderful.

Part of me wishes I could get a much simplified UI for K8s. I use Lens at the moment and while it's very good, it doesn't really smooth over the rough bits of K8s, just kinda organizes and presents them. K8s isn't as bad as a lot of people say once you get past the pain of learning. Still, it misses the mark if what you just want a few simple things Heroku-style instead of every bell and whistle. Small users don't care about ingress, they just want their app to be accessible. Small users aren't interested in namespaces or storage classes or roles. Sure, it's important for K8s to support storage classes for large users who might have all sorts of opinions on how they want their data stored. For a small user, you often just want it stored on the local disk.

Likewise, I think there's a reasonably small set of things people often want to run. For example, the databases Coolify supports (MongoDB, MySQL, PostgreSQL, CouchDB, RedisDB) are probably what 95% of people want. There are K8s operators to run them, but like K8s itself it can often be "here's every knob we could think of, we documented 80% of them, now go write some yaml." Heroku lets me deploy PostgreSQL without that. Why can't I get something a bit more slimmed down like Heroku on K8s - so that if I need the additional power in the future, I can get my hands on it.

I'd even love it if this hypothetical K8s Heroku could commit the yaml it is going to apply to a GitHub repository for me so I can easily track infrastructure changes. It would even let people become more comfortable with K8s as they saw the changes they were making in the UI show up as commits in a repository.

I think the point of this rambling is that Coolify is kinda what people want from one perspective - something that seems nice and friendly and handle the cases that the vast majority of people need solved. However, it lacks the critical mass of K8s which can always leave its future in doubt (it looks like there are two of you on this project and open source can take a toll on people) and without high-availability/multi-server it feels a bit lacking for what so many people are looking for in a self-hosted Heroku. Coolify feels like what I'm looking for - I just want it with high-availability and the possibility of continuing on even if the project shuts down (because I can just use an underlying K8s layer, not because it's open source and I could become the new maintainer).

It feels like there's two camps that don't talk to each other: awesome UX people who know what people want and people building solutions that companies want while scaling up (but end up with a bit of a UX mess).

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.

Deploying AI models into production requires tools that can package applications and manage them at scale. Docker simplifies the deployment of AI applications by containerizing them, ensuring that the application runs smoothly in any environment. Kubernetes, an orchestration system for Docker containers, allows for the automated deployment, scaling, and management of containerized applications, essential for AI applications that need to scale across multiple servers or cloud environments.

To learn more, you can start by exploring the official Kubernetes documentation.

With the containerized Node.js/Express API, I could run multiple containers, scaling to handle more traffic. Using a tool called minikube, we can easily spin up a local Kubernetes cluster to horizontally scale Docker containers. It was possible to keep one shared instance of the database, and many APIs were routed with an internal Kubernetes load balancer.

This package is widely used for powerful CLI builds, it is used for example for Kubernetes CLI and GitHub CLI, in addition to offering some cool features such as automatic completion of shell, automatic recognition of flags (the tags) , and you can use -h or -help for example, among other facilities.

We closely monitor Kubernetes and cloud providers' updates by following official changelogsand using RSS feeds, allowing us to anticipate potential issues and adapt our infrastructure proactively.

"You are holding it wrong", huh?

From the homepage https://kubernetes.io/:

"Kubernetes, also known as K8s, is an open-source system for automating deployment, scaling, and management of containerized applications."

Do you see "not recommended for smaller-scale applications" anywhere? Including on the entire home page? Looking for "small", "big" and "large" also yields nothing.

Open Source and Cloud Computing: A Match Made in Heaven The cloud is accelerating OSS adoption. Cloud-native technologies like Kubernetes [https://kubernetes.io/] and Istio [https://istio.io/], both open-source projects, are revolutionizing how applications are built and deployed across cloud platforms.

If you do kubectl explain deployment than (surprise!) you'll get a description for extensions/v1beta1. Because kubectl explain works the same way, just like kubectl get:

Through the Fast Forward program, we give free services and support to open source projects and the nonprofits that support them. We support many of the world’s top programming languages (like Python, Rust, Ruby, and the wonderful Scratch), foundational technologies (cURL, the Linux kernel, Kubernetes, OpenStreetMap), and projects that make the internet better and more fun for everyone (Inkscape, Mastodon, Electronic Frontier Foundation, Terms of Service; Didn’t Read).

In this project, you will understand and get hands on experience around the entire concept around CI/CD from applications perspective. To fully gain real expertise around this idea, it is best to see it in action across different programming languages and from the platform perspective too. From the application perspective, we will be focusing on PHP here; there are more projects ahead that are based on Java, Node.js, .Net and Python. By the time you start working on Terraform, Docker and Kubernetes projects, you will get to see the platform perspective of CI/CD in action.