You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/device-agent/register.md
+11-9Lines changed: 11 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -147,7 +147,6 @@ flowfuse-device-agent
147
147
You will see the Device Agent start and perform a 'call-home' where it connects back
148
148
to the platform to check what it should be running.
149
149
150
-
151
150
#### Additional Information
152
151
153
152
If you copy or download a **Device Provisioning Configuration** file to your hardware,
@@ -164,12 +163,12 @@ you've followed [Single Device Registration](#single-remote-instance-registratio
164
163
[Bulk Registration](#bulk-registration) to register your device, it will
165
164
automatically be assigned to an Application or Instance.
166
165
167
-
### Applications (Recommended)
168
-
169
-
#### Assign to Application
166
+
### Applications
170
167
171
168
This step will permit you to push Snapshots to your Remote Instance via [DevOps Pipelines](/docs/user/devops-pipelines.md), or via a [Target Snapshot](/docs/user/snapshots/#application-owned-devices) from the Application.
172
169
170
+
#### Assign to Application
171
+
173
172
1. Go to your teams's **Remote Instances** page.
174
173
2. Open the dropdown menu to the right of the Remote Instance you want to assign and
175
174
select the **Add to Application** option.
@@ -206,14 +205,17 @@ NOTE: If you wish to keep the flows currently running on the Remote Instance, it
206
205
207
206
### Hosted Instances
208
207
209
-
This method permits you to set a [Target Snapshot](/docs/user/snapshots/#instance-owned-devices) from the Hosted Instance to the Remote Instance. Note though, you can only push nodes and flows that are supported by _both_ Hosted and Remote Instances. The best use case for Remote Instances are generally to be assigned by an Application instead.
208
+
This method establishes a deployment relationship where a Hosted Instance becomes the source for snapshot deployments to your Remote Instance(s).
209
+
210
+
**Important:** This is a legacy feature; [assigning to Applications](./register.md#applications) is the recommended approach as it provides better fleet management and DevOps Pipeline capabilities. For guidance, see [when to use each approach](/docs/user/concepts.md#when-to-use-instance-assignment-vs-devops-pipelines).
210
211
211
212
#### Assign to Hosted Instance
212
213
213
-
1. Go to your teams's **Remote Instances** page.
214
-
2. Open the dropdown menu to the right of the Remote Instance you want to assign and
215
-
select the **Add to Hosted Instance** option.
216
-
3. Select the instance in the dialog and click **Add** to continue.
214
+
1. Go to your team's **Remote Instances** page.
215
+
2. Open the dropdown menu to the right of the Remote Instance you want to assign and select the **Add to Instance** option.
216
+
3. Select the Hosted Instance in the dialog and click **Add** to continue.
217
+
218
+
**Note:** There are constraints on which instances can be assigned to each other. For detailed information, refer to [Assignment Rules and Constraints](/docs/user/concepts.md#assignment-rules).
If the Remote Instance is behind a HTTP proxy, the agent can be configured to use the proxy by setting the `http_proxy`, `https_proxy` or `all_proxy` environment variables.
@@ -146,4 +153,4 @@ OS and Architecture as your target device, and then copy the modules on to your
146
153
2. Place this file in an empty directory on your local device.
147
154
3. Run `npm install` to install the modules. This will create a `node_modules` directory.
148
155
4. On your target Remote Instance, create a directory called `module_cache` inside the Device Agent Configuration directory.
149
-
5. Copy the `node_modules` directory from your local instance to the target instance so that it is under the `module_cache` directory.
156
+
5. Copy the `node_modules` directory from your local instance to the target instance so that it is under the `module_cache` directory.
0 commit comments