Elgato_dark/fleet
1
0
Fork 0
mirror of https://github.com/fleetdm/fleet synced 2026-05-23 08:58:41 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 111

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
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
docs/01-Using-Fleet/FAQ.md
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?