Files

T

EricandCopilot 562b1978e6 Website: update remediate page for windows users (#43932 )

Closes: https://github.com/fleetdm/fleet/issues/39986

Changes:
- Updated the /remediate page to show a different step 1 for Windows
users.

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

* **New Features**
* Platform-aware remediation UI: the first remediation step now shows
system-tray instructions and a Windows-specific image for Windows
clients, while non-Windows users continue to see the original menu-bar
instructions and image.
* The page now detects Windows clients and surfaces the appropriate
guidance automatically.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

2026-04-21 18:07:07 -05:00

.claude

Website: add claude.md (#43815 )

2026-04-20 18:04:17 -05:00

api

Contact source change for webinar and gated doc (#43838 )

2026-04-21 17:03:41 -05:00

assets

Website: update remediate page for windows users (#43932 )

2026-04-21 18:07:07 -05:00

config

Website: queries » reports (#43871 )

2026-04-21 13:42:32 -05:00

generators/landing-page

Add fleetctl new command (#41909 )

2026-03-20 17:27:27 -05:00

scripts

Website: update build-static-content script to be compatible with Node versions under 20 (#43930 )

2026-04-21 17:31:30 -05:00

tasks

…

views

Website: update remediate page for windows users (#43932 )

2026-04-21 18:07:07 -05:00

.editorconfig

…

.eslintignore

…

.eslintrc

…

.gitignore

…

.htmlhintrc

…

.lesshintrc

…

.npmrc

…

.sailsrc

update marketing handbook page about team roles (#42679 )

2026-03-31 12:33:25 -05:00

app.js

…

Gruntfile.js

…

package-lock.json

Website: update package-lock.json (#43245 )

2026-04-08 10:52:07 -05:00

package.json

Bump jsrsasign from 11.1.0 to 11.1.1 in /website (#42634 )

2026-03-30 11:17:41 -05:00

Procfile

…

README.md

…

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!