- Install w/ npm was missing prereq: install Node.js
- Also use "fleetctl" instead of `fleetctl` when referring the the
tool/noun and not the command
- Added this to the handbook here:
https://github.com/fleetdm/fleet/pull/22397
---------
Co-authored-by: JD <spokanemac@users.noreply.github.com>
Following team feedback from PR #20723.
# Checklist for submitter
If some of the following don't apply, delete the relevant line.
Feedback Row 7: Added warning about lack of centralized logging.
Co-authored-by: Joey Salazar <jgsal@yahoo.com>
This PR closes https://github.com/fleetdm/fleet/issues/21108
@noahtalerman, I double-checked all redirects, and they are working.
Clicking through the URLs in [this
spreadsheet](https://docs.google.com/spreadsheets/d/1djVynIMuJK4pT5ziJW12CluVqcaoxxnCLaBO3VXfAt4/edit?usp=sharing)
is a pretty quick way to go through them all. Note that "Audit logs" and
"Understanding host vitals" redirect to the contributor docs on GitHub,
so they will throw a 404 until this is merged.
Some new guides benefitted from a name change, so they make more sense
as stand-alone guides, and also so that we don't have to mess around
with more redirects later. Those name changes followed [this
convention](https://fleetdm.com/handbook/company/communications#headings-and-titles),
which was recently documented in the handbook.
Have fun!
---------
Co-authored-by: Eric <eashaw@sailsjs.com>
Co-authored-by: Noah Talerman <noahtal@umich.edu>
2024-08-16 15:30:31 -05:00
Renamed from docs/Using Fleet/fleetctl-CLI.md (Browse further)
