7190b74f2f
Closes: #10496 Changes: - Fixed alignment issues with the <scrollable-tweets> component's page indicator (Edge v16 & Safari 10) - Added a hard-coded height to embedded youtube videos in Markdown content to fix it rendering with a height of 0 (Edge v17 & Firefox v54) - Fixed table example syntax highlighting (Edge v17, Chrome v55, Firefox v54, Opera v42, & Safari v10) - Added a set width to the edit page button on tables pages (Safari v10, Firefox v54) - Fixed a bug with the sidebar height on tables pages (Edge v17) - Fixed styling on the pricing calculator inputs (Safari v10 & Firefox v54) - Fixed a layout issue with the pricing calculator call-to-action buttons (Safari v10) - Hid browser-specific form input buttons (Firefox v54) - Fixed the sidebar CTA image on documentation pages (Opera v42) - Fixed a CSS issue with the user story banner on `/platform` (Safari v10, Firefox v54, Chrome v55, Opera v42) - Updated the documentation page script to only copy links to the user's clipboard if the user's browser supports it. - Updated minimum browser versions for Edge, Chrome, and Opera for async functions support. (Edge v16 » Edge v17, Chrome v51 » Chrome v55, Opera v38 » Opera v42) |
||
|---|---|---|
| .. | ||
| api | ||
| assets | ||
| config | ||
| 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
Run the following commands to test the site locally:
npm install -g sails
cd website/
npm install
sails run scripts/build-static-content.js
sails lift
Your local copy of the website is now running at http://localhost:2024!
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!