nebraska
coreroller
| nebraska | coreroller | |
|---|---|---|
| 2 | 1 | |
| 167 | 289 | |
| 3.0% | 0.0% | |
| 8.8 | 10.0 | |
| 3 days ago | over 1 year ago | |
| Go | Go | |
| Apache License 2.0 | GNU General Public License v3.0 or later |
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.
nebraska
-
Flatcar Container Linux
The update server supports the Omaha protocol, is called Nebraska and is available here under an Apache license: https://github.com/kinvolk/nebraska
Our team hosts the public server, but any Flatcar user can run Nebraska themselves and point their nodes to that.
coreroller
-
Flatcar Container Linux
Thanks for dropping the mic, I'll kindly pick it up.
I'm the initiator of the Flatcar Container Linux project and former CEO of Kinvolk. Thus, I'm rather knowledgeable about the project and was involved in most decisions.
The controversy you speak of is very new to me. If you could point to any references I'd love to be aware of that.
Firstly, there was nothing "hacked" out of CoreOS. Flatcar is literally the CoreOS Container Linux repos forked and carried on as is. Once the EOL was reached we started updating the stale packages. That's it. Any further updates are what any distro would do in the course of maintenance to remain modern and relevant.
Secondly, anything that was previously termed the "Pro" version is now just available in the standard version. So there is no difference. To my knowledge, the project doesn't even produce any Pro versions any longer and I don't think there are even any references to it in our docs. But even when we did have a Pro version, all the work we did was done in the open and was in our source repositories. We just didn't release public builds of those.
Unlike CoreOS, we also developed* and open sourced the update server. It's called Nebraska and available here under an Apache license. https://github.com/kinvolk/nebraska
With regard to a license matrix, you can find all licenses for each release in the respective release directory. For example this one: https://stable.release.flatcar-linux.net/amd64-usr/current/f...
If you do find anything that is not 100% open source, let me know and I'll follow up to make sure that's corrected.
I'm happy your excited about your project. But I think you'll fine it's better in the open source space to compete on merit and form relationships rather than tear down other projects and the work of the people behind the projects.
* based on the Core Roller project: https://github.com/coreroller/coreroller
What are some alternatives?
toc - ⚖️ The CNCF Technical Oversight Committee (TOC) is the technical governing body of the CNCF Foundation.
flatcar-website
RPi4 - Raspberry Pi 4 UEFI Firmware Images
coreos-assembler - Tooling container to assemble CoreOS-like systems
Flatcar - Flatcar project repository for issue tracking, project documentation, etc.
docs - Documentation for CoreOS projects
Flatcar - Flatcar project repository for issue tracking, project documentation, etc. [Moved to: https://github.com/flatcar/Flatcar]
fedora-coreos-tracker - Issue tracker for Fedora CoreOS
ostree - Operating system and container binary deployment and upgrades