12bd9ec7dd
* Create Rituals heading and appropriate subheadings ## Growth Rituals ### Social Engagement Ritual: Participate in 50 social media engagements per week. DRI: Drew Baker ### Daily Twitter Ritual: Post FleetDM content on Twitter every weekday. DRI: Drew Baker ### Daily LinkedIn Ritual: Post FleetDM Content to LinkedIn every weekday. DRI: Drew Baker ### osQuery Jobs Ritual: Post to @osqueryjobs two times per week. DRI: Drew Baker ### Enriching Leads Ritual: Follow the Lead Enrichment Process every Friday. DRI: Drew Baker ### Outside Contributions Ritual: Check PRs for outside contributions every Monday. DRI: Drew Baker ### Weekly Blogpost Ritual: Publish FleetDM blog post once per week. Promote blog posts on socials once per week. ### Weekly Ins and Outs Ritual: Track ins and outs once per week. DRI: Tim Kern ### Podcast Outreach Ritual: Conduct podcast outreach twice per week. DRI: Drew Baker ### Monthly Conference Ritual: Check for conference openings and for conference sponsorships on the 1st of every month. DRI: Drew Baker * Update growth.md * Convert entries to table format This works in the preview. * Update growth.md * Table format revision Reformatted table in accordance with suggestions from Mike T. * Update handbook/growth.md * Update handbook/growth.md * Update handbook/growth.md * Update handbook/growth.md * Update handbook/growth.md * Update handbook/growth.md * Update handbook/growth.md * Update handbook/growth.md * Update handbook/growth.md * Update handbook/growth.md * Update handbook/growth.md * Update handbook/growth.md * Update handbook/growth.md Co-authored-by: Tim Kern <tim@fleetdm.com> Co-authored-by: Mike Thomas <78363703+mike-j-thomas@users.noreply.github.com>
Website News Report a bug
Fleet is the most widely used open source osquery manager. Deploying osquery with Fleet enables programmable live queries, streaming logs, and effective management of osquery across 100,000+ servers, containers, and laptops. It's especially useful for talking to multiple devices at the same time.
Try Fleet
With Node.js and Docker installed:
# Install the Fleet command-line tool
sudo npm install -g fleetctl
# Run a local demo of the Fleet server
sudo fleetctl preview
Windows users can omit
sudo, and should run the command inCmd/PowerShellas administrators.
The Fleet UI is now available at http://localhost:1337.
Now what?
Check out the Ask questions about your devices tutorial to learn where to see your devices in Fleet, how to add Fleet's standard query library, 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 latest release from this repository (it'll work out of the box).
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.
