Mike Thomas 3eeade1fb3 Updated formatting for downgrade instructions (#10527)
I noticed an opportunity to improve the formatting of the downgrading to
Fleet Free instructions while I was linking to the section from another
task.

- Highlighted renewal/contact instructions as a note
- Emphasised each of the main steps
- Removed redundant language
- Removed redundant line breaks in the markdown
- Increased spacing between steps
2023-04-13 09:41:24 +09:00
2023-04-11 15:19:03 -04:00
2023-04-12 17:03:09 -05:00
2023-04-12 17:03:09 -05:00
2023-04-12 16:11:04 -03:00
2023-04-12 16:11:04 -03:00
2023-04-05 20:49:02 -03:00
2023-04-12 17:03:09 -05:00
2023-03-15 15:27:57 -05:00
2023-04-12 17:03:09 -05:00
2022-05-05 20:29:06 -05:00

Fleet logo, landscape, dark text, transparent background

Website   News   Report a bug

Run Tests   Go Report Card   CII Best Practices   Twitter Follow  

Fleet is the lightweight, open source telemetry platform for servers and workstations. Deploy osquery with Fleet to get comprehensive, customizable data from all your devices and operating systems without the downtime risk.

Try Fleet

Head to fleetdm.com/try-fleet to fire up a one-off cloud instance for quickly trying out Fleet.

Now what?

Check out the Learn how to use Fleet doc to learn how to add your device to Fleet and how to ask questions about your devices by running queries.

Team

Fleet is independently backed and actively maintained with the help of many amazing contributors.

📖 In keeping with our value of openness, Fleet Device Management's company handbook is public and open source. You can read about the history of Fleet and osquery and our commitment to improving the product. To upgrade from Fleet ≤3.2.0, just follow the upgrading steps for the earliest subsequent major release from this repository (it'll work out of the box until the release of Fleet 5.0).

Documentation

Documentation for Fleet can be found here.

Community

Chat

Please join us in the #fleet channel on osquery Slack.

Contributing

Contributions are welcome, whether you answer questions on Slack/GitHub/StackOverflow/Twitter, improve the documentation or website, write a tutorial, give a talk, start a local osquery meetup, troubleshoot reported issues, or submit a patch. The Fleet code of conduct is on GitHub.

Banner featuring a futuristic cloud city with the Fleet logo

S
Description
No description provided
Readme MIT
1.6 GiB
Languages
Go 52.5%
TypeScript 37.5%
JavaScript 4.3%
PowerShell 1.4%
Augeas 0.9%
Other 3%