Discharge7443/fleet
1
0
Fork 0
Code Issues Pull Requests Actions 6 Packages Projects Releases Wiki Activity

Brand guidelines: “FleetDM” >> “Fleet” or “Fleet Device Management” (#3903)

Browse Source 
* Brand guidelines: “FleetDM”  >> “Fleet” or “Fleet Device Management”

* Update FAQ.md
This commit is contained in:
Mike McNeil
2022-01-27 12:50:18 -06:00
committed by GitHub
parent 1667fdcf22
commit d79f27a7a5
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/01-Using-Fleet/FAQ.md
+2 -2
View File
@@ -23,9 +23,9 @@
The upgrade from kolide/fleet to fleetdm/fleet works the same as any minor version upgrade has in the past.
Minor version upgrades in Kolide Fleet often included database migrations and the recommendation to back up the database before migrating. The same goes for FleetDM Fleet versions.
Minor version upgrades in Kolide Fleet often included database migrations and the recommendation to back up the database before migrating. The same goes for the new Fleet.
To migrate from Kolide Fleet to FleetDM Fleet, please follow the steps outlined in the [Upgrading Fleet section](../02-Deploying/06-Upgrading-Fleet.md) of the documentation.
To migrate from `kolide/fleet` to the new Fleet, please follow the steps outlined in the [Upgrading Fleet section](../02-Deploying/06-Upgrading-Fleet.md) of the documentation.
## Has anyone stress tested Fleet? How many clients can the Fleet server handle?