mirror of
https://github.com/empayre/fleet.git
synced 2024-11-06 08:55:24 +00:00
Update Launcher difference README
Indicate that Orbit shares no code with Launcher
This commit is contained in:
parent
995c8b18e0
commit
adcae02409
@ -163,7 +163,7 @@ After successful notarization, the generated "ticket" is automatically stapled t
|
||||
|
||||
### How does Orbit compare with Kolide Launcher?
|
||||
|
||||
Orbit is inspired by the success of [Kolide Launcher](https://github.com/kolide/launcher), and approaches a similar problem domain with new strategies informed by the challenges encountered in real world deployments.
|
||||
Orbit is inspired by the success of [Kolide Launcher](https://github.com/kolide/launcher), and approaches a similar problem domain with new strategies informed by the challenges encountered in real world deployments. Orbit does not share any code with Launcher.
|
||||
|
||||
- Both Orbit and Launcher use [The Update Framework](https://theupdateframework.com/) specification for managing updates. Orbit utilizes the official [go-tuf](https://github.com/theupdateframework/go-tuf) library, while Launcher has it's own implementation of the specification.
|
||||
- Orbit can be deployed as a (near) drop-in replacement for osquery, supporting full customization of the osquery flags. Launcher heavily manages the osquery flags making deployment outside of Fleet or Kolide's SaaS difficult.
|
||||
|
Loading…
Reference in New Issue
Block a user