Elgato_dark/fleet
1
0
Fork 0
mirror of https://github.com/fleetdm/fleet synced 2026-04-21 13:37:30 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 91
fleet/website
History
Eric 34914a8aab
Website: Update article blockquote styles (#32159) 
Closes: #29516

Changes:
- Updated blockquote styles on article pages.
2025-08-22 13:27:31 -05:00
..
api Website: Fix ad attribution when creating historical event records (#32211) 2025-08-22 11:36:49 -05:00
assets Website: Update article blockquote styles (#32159) 2025-08-22 13:27:31 -05:00
config Track SDLC metrics. (#31409) 2025-08-19 13:24:54 -05:00
generators/landing-page Clean up "click here" and "here" link anchors - part 1 (#29731) 2025-06-04 13:54:34 -06:00
scripts Website: Add primaryBuyingSituation migration script. (#31494) 2025-08-01 17:07:27 -05:00
tasks Move fleetdm.com into main Fleet repo (#83) 2020-12-02 14:48:03 -06:00
views Website: Update configuration builder (#32165) 2025-08-21 13:04:39 -05:00
.editorconfig Move fleetdm.com into main Fleet repo (#83) 2020-12-02 14:48:03 -06:00
.eslintignore add back public storybook site build step (#12746) 2023-07-13 17:44:41 +01:00
.eslintrc Website: Add android proxy endpoints (#28267) 2025-06-12 13:23:49 -05:00
.gitignore fix gitignore 2021-05-11 16:01:25 -05:00
.htmlhintrc Move fleetdm.com into main Fleet repo (#83) 2020-12-02 14:48:03 -06:00
.lesshintrc Move fleetdm.com into main Fleet repo (#83) 2020-12-02 14:48:03 -06:00
.npmrc Move fleetdm.com into main Fleet repo (#83) 2020-12-02 14:48:03 -06:00
.sailsrc Gtm groups (#27614) 2025-03-28 11:06:05 -05:00
app.js Move fleetdm.com into main Fleet repo (#83) 2020-12-02 14:48:03 -06:00
Gruntfile.js Move fleetdm.com into main Fleet repo (#83) 2020-12-02 14:48:03 -06:00
package.json Track SDLC metrics. (#31409) 2025-08-19 13:24:54 -05:00
Procfile Dedupe setting of env var (#87) 2020-12-03 16:11:46 -06:00
README.md Create CEO and People pages and reorg (#31559) 2025-08-04 13:07:18 -05:00

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, create an issue in the fleet GitHub repository.

Testing locally

See https://fleetdm.com/handbook/engineering#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 run and npm run commands in there do, check the scripts in website/package.json and in website/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!