* Create introducing-sandbox:-the-fastest-way-to-play-with-fleet.md
* Update articles/introducing-sandbox:-the-fastest-way-to-play-with-fleet.md
Co-authored-by: Chris McGillicuddy <108031970+chris-mcgillicuddy@users.noreply.github.com>
* added image and video
- added image and video
- updated meta tags
* Update introducing-sandbox:-the-fastest-way-to-play-with-fleet.md
- removed comma from meta tag title
* Rename file, update quotation marks
Co-authored-by: Chris McGillicuddy <108031970+chris-mcgillicuddy@users.noreply.github.com>
Co-authored-by: Mike Thomas <mthomas@fleetdm.com>
Co-authored-by: Eric <eashaw@sailsjs.com>
this adjusts the TestInstallerHeadCheck check to use `DoRaw` instead of `Do`, which sends a body with null when nil is passed for the params parameter.
Updated migration used to increate the width of 'software.vendor' to
address issue found when running migration in aurora: "ALGORITHM=INPLACE is not
supported. Reason: cannot silently convert NULL values, as required in
this SQL_MODE. Try ALGORITHM=COPY."
- Updated "Try it out" CTA to point to Sandbox.
- Updated "Try Fleet" to "Sandbox" to avoid repetition and have continuity across the CTAs.
- Updated "Join the community" to "Community" for continuity across the CTAs.
- Update "Learn how to use Fleet" docs page to walk a Fleet Sandbox user through adding their device and running a query
- Add a "Get operating system information" query to standard query library for the "Learn how to use Fleet" walkthrough
- Update Fleet's top level README to point users who want to try Fleet to Fleet Sandbox
- Update "How to install osquery..." (macOS, Windows, Linux) blog posts to point users who want to try Fleet to Fleet Sandbox
- Move `fleetctl preview` questions to "Contributing" FAQ section in docs. This is because `fleetctl preview` is now a testing tool for Fleet contributors
- Update "Deploying" docs to point users who want to try Fleet to Fleet Sandbox
* Codeowners: Reduce # of pings for reviews of docs
To avoid duplicative pings in Slack, reduce the number of folks who get automatically pinged about review requests when documentation, handbook, and website routes are changed.
I left Mike T and Chris both on the digital experience handbook so that PRs can be merged quickly there in many cases, regardless of timezone.
Also @chris-mcgillicuddy I made you responsible for either (a) approving and merging or (b) if there changes to meaning or code samples, requesting review from the on-call engineer.
* Update to reflect routing doc changes through Chris, and add sub-headings
* Pull the most relevant sentences to the top of each responsibility
* Use more peaceful language
* improve error handling in vulnerabilities cron
* fix tests
* Use errHandler and go mod tidy
* Add dep that got removed by mod tidy
* add dsl to tools
* Add changes file
Co-authored-by: Michal Nicpon <michal@fleetdm.com>
Co-authored-by: Tomas Touceda <chiiph@gmail.com>
