Skip to content

Commit

Permalink
DOCS-1848: Support nested fragmentes
Browse files Browse the repository at this point in the history
  • Loading branch information
npentrel committed Jan 16, 2025
1 parent 2c7e413 commit 956de68
Showing 1 changed file with 2 additions and 1 deletion.
3 changes: 2 additions & 1 deletion docs/manage/fleet/reuse-configuration.md
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,6 @@ Fragments are a way of sharing and managing [machine configurations](/operate/ge

For example, if you have a fleet of rovers that uses the same hardware, you could use a fragment to configure the motors, base component, camera, and all other resources for all rovers.
If some of the rovers have a slightly different configuration, you can overwrite the configuration for just those {{< glossary_tooltip term_id="resource" text="resources" >}} of those rovers.

If one rover has an arm attached, you can add the rover configuration fragment (including the motors, camera, and base components), and then configure the arm on just that one rover.

## Create a fragment
Expand All @@ -40,6 +39,8 @@ You must be an [organization owner](/manage/manage/rbac/) to create fragments fo
Start by configuring one of your machines.

In the [Viam app](https://app.viam.com), use the **CONFIGURE** tab to build a configuration for all resources you want to use on all your machines.
You can use all available resources except [triggers](/data-ai/data/advanced/alert-data/) in the configuration for your machine.
This means you can also use fragments inside a fragment.

{{<imgproc src="/how-tos/one-to-many/config.png" resize="800x" class="fill aligncenter" style="width: 400px" declaredimensions=true alt="Configuration builder UI">}}

Expand Down

0 comments on commit 956de68

Please sign in to comment.