Files

T

Eric 48f8fb733e Website: add /download page (#45504 )

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

Changes:
- Added /download, a page that has links to download the fleetctl
installers included in the latest release
- Updated the build-static-content script to send a request to GitHub to
get the download URLs of the latest released fleetctl installers.
- Update the parallax-city component to support a new prop that removes
the component's background when set.

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

* **New Features**
* Added a dedicated /download page with platform-specific installer
links, FAQ accordion, and copy-to-clipboard for code snippets (copy
buttons removed if unsupported).
  * Added shortlink redirect from /downloads → /download.
  * Sitemap now includes /download for better discoverability.

* **Style**
* New page styles and component styles, plus an option to render the
parallax city without a background.

* **Chores**
* Build now fetches and populates installer URLs automatically; the
download route is publicly accessible.

<!-- review_stack_entry_start -->

[![Review Change
Stack](https://storage.googleapis.com/coderabbit_public_assets/review-stack-in-coderabbit-ui.svg)](https://app.coderabbit.ai/change-stack/fleetdm/fleet/pull/45504)

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

2026-05-14 12:41:27 -05:00

.claude

…

api

Website: add /download page (#45504 )

2026-05-14 12:41:27 -05:00

assets

Website: add /download page (#45504 )

2026-05-14 12:41:27 -05:00

config

Website: add /download page (#45504 )

2026-05-14 12:41:27 -05:00

generators/landing-page

…

scripts

Website: add /download page (#45504 )

2026-05-14 12:41:27 -05:00

tasks

…

views

Website: add /download page (#45504 )

2026-05-14 12:41:27 -05:00

.editorconfig

…

.eslintignore

…

.eslintrc

…

.gitignore

…

.htmlhintrc

…

.lesshintrc

…

.npmrc

Add npm min release age (#45268 )

2026-05-13 10:20:13 -04:00

.sailsrc

…

app.js

…

Gruntfile.js

…

package-lock.json

…

package.json

…

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!