- Add a new "Configuration for contributors" doc page. Move settings that are not recommended for production use
- Remove settings modified in the `config` YAML document from the deploying/configuration doc page
- Document all keys in `config` and `teams` YAML documents
- Add comments to several `.go` files and remove unused struct
Replaced with the osquery/#fleet invite link.
Osquery.fleetdm.com has roughly a 67% bounce rate, and a 14% conversion rate to clicks to this link, when people are actively clicking a CTA to join. Growth & DX believes we can grow Fleet's community faster by testing removing this intermediate page.
Replaced with "Osquery slack" and a link to https://osquery.fleetdm.com/
This will allow us to still link to this subdomain in the main nav while also changing Fleetdm.com/slack redirects to the osquery/#fleet invite link
This fixes an unreleased bug I introduced in eeefe2, as the config colum in the teams table is nulleable, it unmarshalls into nil and we can't dereference the variable
* cloud.gov deployment
Adds example manifest.yml file and docs covering steps to deploy fleetdm to cloud.gov
* rename manifest
rename manifest and small edits
As stated by the title, this fixes a bug in token rotation caused by a file having existing read-only permissions. This affects Fleet Desktop after is upgraded if an existing Orbit created a file that's not accessible by non-root users.
I have also included 77a59ac to fix an URL format
* Handbook: adding contact information for customers
I added information for free and paying customers to contact Fleet for support.
* Update README.md
Co-authored-by: Mike Thomas <78363703+mike-j-thomas@users.noreply.github.com>
In https://github.com/fleetdm/fleet/pull/7399 we accidentally:
1. added a condition to `.github/workflows/fleet-and-orbit.yml` that always evaluates to `false` making this workflow always fail
2. modified the condition of `.github/workflows/fleetctl-preview-latest.yml`
This reverts those changes.
* Copy tweak
Not sure this is the right language, but just something to get it started, up to Chris
Feedback/reasoning:
- "to over" or "into over"?
- "over" + specific number seems overly marketing-ish
- maybe "gives visibility to Fortune 1000 companies, and is powering over 1 million…"
* Update homepage.ejs
Co-authored-by: Chris McGillicuddy <108031970+chris-mcgillicuddy@users.noreply.github.com>
- Removed mention of "Fortune 1000 companies" in copy to keep "1.65 million" figure
- Logos at the bottom of hero banner convey that Fleet is used by Fortune 1000 companies
Martin Angers