Related: #39896 Context: I found that we use `FLEET_SOFTWARE_INSTALLER_STORE_DIR` env variable in [render.yaml](https://github.com/fleetdm/fleet/blob/9b51376f83af8c7c2b2335ff0a1ab146ae13238f/render.yaml#L15). S3 is the best practice and should be used in production, we even have a [log](https://github.com/fleetdm/fleet/blob/9d0f510a8db6a470ecf83cc0076680c4d518ea7e/cmd/fleet/serve.go#L568) that says that. Since we officially support Render deployment, and Render doesn't support S3, I think we should document this exception. More context: https://fleetdm.slack.com/archives/C051QJU3D0V/p1785496835774739 --------- Co-authored-by: Noah Talerman <47070608+noahtalerman@users.noreply.github.com> Co-authored-by: Robert Fairburn <8029478+rfairburn@users.noreply.github.com>
Configuration
Fleet server
Fleet server configuration
Documentation for configuring the Fleet binary, managing osquery configurations, and running with systemd.
Agent
Agent configuration
Learn how to set agent options with config YAML file and the fleetctl command line tool.