orange-cat
fleet
| orange-cat | fleet | |
|---|---|---|
| - | 9 | |
| 182 | 2,438 | |
| - | - | |
| 0.0 | 0.0 | |
| - | - | |
| Go | Go | |
| - | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
orange-cat
We haven't tracked posts mentioning orange-cat yet.
Tracking mentions began in Dec 2020.
fleet
-
Ask HN: Abandoned/dead projects you think died before their time and why?
systemd-fleet, by the original CoreOS folks. https://github.com/coreos/fleet
I used this when it was brand new for a bit and it was so incredibly smooth and worked so well. It solved the problem of controlling systemd units remotely so well. I'm pretty sure the only reason it never actually took off was kubernetes and coreos's acquisition, however it actively solves the 'other half' of the k8s problem which is managing the state of the host itself.
- Replacing Kubernetes with Systemd
-
Podman Quadlets with Podman Desktop
This made me remember Fleet[0], which I used in the past on CoreOS. It was a very good abstraction for my simple cluster. It felt as robust as a managed cloud service. It's a shame it didn't catch on (and also what happened to CoreOS).
[0] https://github.com/coreos/fleet
-
We clone a running VM in 2 seconds
We were working on this at CoreOS before Kubernetes came about – called fleet https://github.com/coreos/fleet. Distributed systemd units run across a cluster, typically running containers or golang binaries with a super minimal OS underneath. I always thought it was cool but it definitely had its challenges and Kubernetes is better in most ways, IMO.
-
The 2024 Web Hosting Report
Docker didn’t have a default way to run on multiple hosts, and so in the wake of docker’s explosive adoption there was a rush of different solutions offered for scheduling containers across a fleet. One of the first well-adopted solutions was actually called fleet - it was part of CoreOS, whose team went on to be very influential throughout the container revolution. This was in the systemd era, and was basically seen as a multi-host systemd. It was very cool and it worked great!
-
The Container Orchestrator Landscape
Figure out how to revive https://github.com/coreos/fleet as something native in systemd?
-
Kubernetes is just Systemd distributed just like /etc is ETCD(istributed)
I guess what in trying to say is k8s is systemd distributed but more then. I see how in line fleet and systemd is though https://github.com/coreos/fleet/blob/master/Documentation/fleet-k8s-compared.md
-
We Don’t Use Docker (We Don’t Need It)
What you describe is essentially the original CoreOS fleet[0] project. It's distributed systemd init files.
[0] https://github.com/coreos/fleet#fleet---a-distributed-init-s...
I find it ironic half of k8s mojo, etcd, came out of this project as well.
What are some alternatives?
limetext - Open source API-compatible alternative to the text editor Sublime Text
ide - A Go code editor. With debugging and Autocomplete. 一个 Go 代码编辑器，具有 DEBUGGING 和 AUTOCOMPLETE
ipe - An open source Pusher server implementation compatible with Pusher client libraries written in GO
peg - Peg, Parsing Expression Grammar, is an implementation of a Packrat parser generator.
nes - NES emulator written in Go.
borg - Search and save shell snippets without leaving your terminal