Local Storage Capability

Local storage access provides engineers with a dedicated persistent directory for storing critical assets like maps and models that must survive deployment cycles.

Prior to supporting local storage, every Chassy deployment to fleets would result in a new immutable deployment of code and data with no option to persist them beyond the lifespan of a deployment. With this new ability you can mark packages intended to be deployed in a release as persistent, and also write application data directly to the persistent directory /persistent for use later. This is ideal for storing large artifacts such as maps and personalized user configurations.

Key Benefits:

• Persistent storage of maps and models across deployments

• Reduced deployment time by eliminating redundant data uploads

• Improved operational continuity for production systems

• Enhanced data management capabilities for engineering teams

Prerequisites and Compatibility

Any machines enrolled before August 1, 2025 must be re-enrolled to Chassy to enable local storage functionality. Follow the instructions on the Enrolling Machinesguide and run the enrollment script again to re-enroll your devices.

Fleets created after August 1, 2025 will have this feature automatically enabled.

To check if your fleet is compatible, go to the Fleets panel of Chassy Console, and click on your fleet. If the fleet was created before August 1, 2025, you'll see an option to Enable local storage in the fleet settings on the side panel.

Confirm enabling Local Storage on the pop up modal. If successful, a notification will pop up saying "Fleet was successfully updated," and the option to Enable local storage in the fleet settings will disappear.

How to Use Persistent Storage

To utilize this new feature, simply direct your code to save any files to the /persistent directory on the target device.

Chassy does not impose any limitations on file size or types, but be aware of your machines' remaining memory space.