Based on our record, Rancher should be more popular than Flox. It has been mentiond 24 times since March 2021. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.
I don't know in which extend you plan to use Kubernetes in the future, but if it is aimed to become several huge production clusters, you should looks into Apps like Rancher: https://rancher.com. Source: almost 3 years ago
But I think once you have a good understanding of K8S internal (components, how thing work underlying, etc.), you can use some tool to help you provision / maintain k8s cluster easier (look for https://rancher.com/ and alternatives). Source: almost 3 years ago
A few years, I would have said no. Now, I'm cautiously optimistic about it. Personally, I think that you can use something like Rancher (https://rancher.com/) or Portainer (https://www.portainer.io/) for easier management and/or dashboard functionality, to make the learning curve a bit more approachable. For example, you can create a deployment through the UI by following a wizard that also offers you... - Source: Hacker News / almost 3 years ago
Alternatively, it is also possible to use a multi-cloud or hybrid-cloud approach, which combines several cloud providers or even public and private clouds. Special tools such as Rancher and OpenShift can be very useful to run this type of system. - Source: dev.to / almost 3 years ago
Rancher provides a Rancher authentication proxy that allows user authentication from a central location. With this proxy, you can set the credential for authenticating users that want to access your Kubernetes clusters. You can create, view, update, or delete users through Rancher’s UI and API. - Source: dev.to / almost 3 years ago
- `flox activate` -> get to work The reason we call these "environments" instead of "developer environments" is that what we provide is a generalization of developer environments, so they're useful in more than just local development contexts. For example, you can use Flox to replace Homebrew by creating a "default" environment in your home directory [2]. You can also bundle an environment up into a container [3]... - Source: Hacker News / 20 days ago
Is the objective to get inside a container to do dev stuff? Reminds me of https://www.jetify.com/devbox and https://flox.dev/. - Source: Hacker News / 2 months ago
I think it's a bad addition since it pushes people towards a worse solution to a common problem. Using "go tool" forces you to have a bunch of dependencies in your go.mod that can conflict with your software's real dependency requirements, when there's zero reason those matter. You shouldn't have to care if one of your developer tools depends on a different version of a library than you. It makes it so the tools... - Source: Hacker News / 4 months ago
I think that's a bit reductive, but I get the intent. A lot of people see systemic problems in their development and turn to tools to reduce the cognitive load, busywork, or just otherwise automate a solution. For example "we always argue over formatting" -> use an automated formatter. That makes total sense as long as managing/interacting with the tool is less work, not just different work. With Nix I still think... - Source: Hacker News / 5 months ago
Try flox [0]. It's an imperative frontend for Nix that I've been using. I don't know how to use nix-shell/flakes or whatever it is they do now, but flox makes it easy to just install stuff. [0]: https://flox.dev/. - Source: Hacker News / 5 months ago
Kubernetes - Kubernetes is an open source orchestration system for Docker containers
Podman - Simple debugging tool for pods and images
Terraform - Tool for building, changing, and versioning infrastructure safely and efficiently.
devenv - Fast, Declarative, Reproducible, and Composable dev envs
Puppet Enterprise - Get started with Puppet Enterprise, or upgrade or expand.
DevBox - Everyday utilities for the everyday developer