Files

T

Eric 1563aeb70c Website: improve speed of deliver-talk-to-us-form-submission action (#50593 )

Changes:
- Updated the model used in the prompt helper calls in the
deliver-talk-to-us-form-submission action and the get-enriched helper to
improve the speed of routing users booking a demo.

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

## Summary by CodeRabbit

* **Improvements**
* Updated location and address enrichment to use an updated language
model, improving the processing of submitted information while
preserving existing form behavior.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->

2026-08-05 11:42:13 -05:00

.claude

…

api

Website: improve speed of deliver-talk-to-us-form-submission action (#50593 )

2026-08-05 11:42:13 -05:00

assets

Remove Fig FMA (cask removed from Homebrew upstream) (#50483 )

2026-08-04 07:19:45 -05:00

config

[Route] Update routes.js (#50472 )

2026-08-04 07:11:56 -06:00

generators/landing-page

…

scripts

Website: use git to get lastModifiedAt timestamps for markdown and yaml files, show last updated date on article pages (#48918 )

2026-07-09 13:18:56 -05:00

tasks

…

views

Website: update contact form button (#50477 )

2026-08-03 17:52:25 -05:00

.editorconfig

…

.eslintignore

…

.eslintrc

…

.gitignore

…

.htmlhintrc

…

.lesshintrc

…

.npmrc

…

.sailsrc

…

app.js

…

go.mod

…

Gruntfile.js

…

package-lock.json

Website: update package.json overrides, update package-lock (#49852 )

2026-07-27 13:41:22 -05:00

package.json

Website: update package.json overrides, update package-lock (#49852 )

2026-07-27 13:41:22 -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!