Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.mirurobotics.com/llms.txt

Use this file to discover all available pages before exploring further.

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
Select the release we just created and hit Next.
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, open a terminal on the machine being deployed to and run cat on the file path of a given config instance. 
cat /srv/miru/configs/mobility.json
You should find that the editor’s content is identical to the config instance on the machine.

​
Patch a deployment

To edit a config instance, make some changes to the current deployment in the editor. As edits are made, a log on the right maintains a list of all changes, categorizing them by their type: added, deleted, or modified.
Deployment Editor Modifications
Only the latest deployment may be edited; all others are read-only.
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 May 18, 2026