Skip to main content
We’re ready to deploy config instances to a device. Navigate back to the Devices page and click into the device we provisioned in the previous step.
Provisioned Device
The Set Release dialog opens. Select the release we just created and click Select.
A release can only be deployed to devices running the operating system its file paths target. Make sure the release was created from the getting-started folder (linux/ or windows/) that matches the device’s operating system.
Set Release Dialog
Input the desired parameters for the Mobility, Planning, and Communication config instances respectively.
Initial Deployment Editor Draft Page
The instances are auto-populated with the default values defined in the release’s config schemas. If using empty schemas, the auto-populated instances will be empty as well.
Finally, click Deploy in the top right, provide a description, and confirm the device name to deploy.
Initial Deployment Deploy Dialog

​
Verify the deployment

To verify the config instances seen in the editor are deployed to the device, print the contents of a config instance on the machine being deployed to.
Open a terminal on the device and run cat on the file path of a given config instance.
You should find that the editor’s content is identical to the config instance on the machine.

​
Update the configs

To edit a config instance, make some changes in the editor. The Draft panel on the right lists each change as added, modified, or deleted.
Deployment Editor Modifications
Once you are satisfied with the edits, click Deploy in the top right. As before, fill out the deployment dialog and click Deploy.
Deployment Editor Deploy Dialog
Congratulations! You’ve successfully deployed configurations to a device with Miru!
Last modified on October 9, 2026