fleet/docs
noahtalerman 19816cee1a
Add help text within user actions dropdown menu. Update copy in API documentation. (#142)
- Add help text within dropdown in smaller font size underneath "Require password reset" saying "This will revoke all active Fleet API tokens for this user."
- Update API docs to use "API token" parlance instead of "Auth token"
2020-12-21 15:47:35 -08:00
..
api Add help text within user actions dropdown menu. Update copy in API documentation. (#142) 2020-12-21 15:47:35 -08:00
architecture Add template and directory for ADRs (#1807) 2018-06-04 09:39:50 -06:00
cli Change name to Fleet in documentation. (#77) 2020-12-01 13:34:08 -05:00
dashboard Change name to Fleet in documentation. (#77) 2020-12-01 13:34:08 -05:00
development Add fleetctl.exe.zip to release process (#80) 2020-12-02 08:24:34 -08:00
images Update SAML documentation (#2113) 2019-10-11 15:14:56 -07:00
infrastructure Add information on datastore options in Fleet to FAQ. (#136) 2020-12-16 16:20:38 -08:00
README.md Change name to Fleet in documentation. (#77) 2020-12-01 13:34:08 -05:00

Fleet Documentation

Welcome to the documentation for the Fleet osquery fleet manager.

  • If you're interested in using the fleetctl CLI to manage your osquery fleet, see the CLI Documentation.
  • Resources for deploying osquery to hosts, deploying the Fleet server, installing Fleet's infrastructure dependencies, etc. can all be found in the Infrastructure Documentation.
  • If you are interested in accessing the Fleet REST API in order to programmatically interact with your osquery installation, please see the API Documentation.
  • Information about using the Fleet web dashboard can be found in the Dashboard Documentation.
  • Architecturally significant decisions are documented in the Architecture Documentation.
  • Finally, if you're interested in interacting with the Fleet source code, you will find information on modifying and building the code in the Development Documentation.

If you have any questions, please don't hesitate to File a GitHub issue or join us on Slack. You can find us in the #fleet channel.