c9e476bfa0
Updated incorrect/outdated descriptions and links. Closes https://github.com/fleetdm/fleet/issues/17022. - Okta - Updated description: Enable single sign-on (SSO) by configuring Fleet as an Okta SAML application. - Active Directory - Updated description: Integrate with a legacy on-prem identity server. - Removed the docs links since there is currently no official Fleet integration for this. - Azure - Updated description: Deploy your own self-managed Fleet server on Azure. - Updated the link to point to community support since we don’t have documentation. - Ansible - Updated description: Deploy Fleet with Ansible. - Chef - Updated description: Chef is an automation tool that can be used with Fleet. - Removed the docs link since we don’t have an integration like the Puppet module for Chef. The existing link pointed to an irrelevant Chef reference. - Google Cloud Platform - Updated description: Deploy your own self-managed Fleet server on Google Cloud Platform (GCP). - Updated the link to point to community support since we don’t have documentation. - AWS - Updated the link Link to point to the deploy docs: [/docs/deploy/deploy-fleet#aws](/docs/deploy/deploy-fleet#aws) - Munki - Updated description: Deploy software with Fleet and Munki. - Puppet - Updated description: Deploy configuration profiles and issue MDM commands with Fleet and Puppet. |
||
|---|---|---|
| .. | ||
| api | ||
| assets | ||
| config | ||
| generators/landing-page | ||
| scripts | ||
| tasks | ||
| views | ||
| .editorconfig | ||
| .eslintignore | ||
| .eslintrc | ||
| .gitignore | ||
| .htmlhintrc | ||
| .lesshintrc | ||
| .npmrc | ||
| .sailsrc | ||
| app.js | ||
| Gruntfile.js | ||
| package.json | ||
| Procfile | ||
| README.md | ||
fleetdm.com
This is where the code for the public https://fleetdm.com website lives.
Bugs
To report a bug or make a suggestion for the website, click here.
Testing locally
See https://fleetdm.com/handbook/digital-experience#test-fleetdm-com-locally
Deploying the website
To deploy changes to the website to production, merge changes to the main branch. If the changes affect the website's code, or touch any files that the website relies on to build content, such as the query library, osquery schema, docs, handbook, articles, etc., then the website will be redeployed.
Wondering how this works? This is implemented in a GitHub action in this repo. Check out the code there to see how it works! For help understanding what
sails runandnpm runcommands in there do, check the scripts inwebsite/package.jsonand inwebsite/scripts/.
Changing the database schema
To deploy new code to production that relies on changes to the database schema or other external systems (e.g. Stripe), first put the website in "maintenance mode" in Heroku. Then, make your changes in the database schema. Next, if you have a script to fix/migrate existing data, go ahead and run it now. (e.g. sails run fix-or-migrate-existing-data). Then, merge your changes and wait for the deploy to finish. Finally, switch off "maintenance mode" in Heroku.
Note that entering maintenance mode prevents visitors from using the website, so it should be used sparingly, and ideally at low-traffic times of day.
Warning: Doing an especially sensitive schema migration? There is a potential timing issue to consider, thanks to an infrastructure change that eliminated downtime during deploys by using Heroku's built-in support for hot-swapping. Read more in https://github.com/fleetdm/fleet/issues/6568#issuecomment-1211503881
Wiping the production database
I hope you know what you're doing. The "easiest" kind of database schema migration:
sails_datastores__default__url='REAL_DB_URI_HERE' sails run wipe
Then when you see the sailboat, hit CTRL+C to exit. All done!