Component settings let you set the location of the server where the component will run. 


If you're hovering the cursor over a component in the dataflow, you'll see a toolbar below it.



Or, if the component is expanded, click on the ellipsis. 

pXbBXUKd8MDRdKi4kO2ZipsCYTOVPXoXoA.png

The equalizer icon, 96ksR6aStpdsIgcS4PJlCFZAxcM5XAUzcw.png, opens a component settings window. Component settings, in this case, is just configuring the location of the server that an R or Python component runs on in a given xap (For configuring inputs of components, please see Dataflow User Interface and the documentation section for components.) 


Component settings are per component instance, so each new component instance will have its own set of settings. These settings are saved with the xap and restored when the xap is reopened.


Each setting is a key-value pair. If not set, it will use the default setting set by the component author.


runEnv is the expression used for server-side components to specify where the component is run. 

 

To run the component in a docker container:

"runEnv": {
  "type": "docker"
}

 

To run the component on a remote server:

"runEnv": {
  "type": "remote",
  "host": "192.168.0.1",
  "port": 10000
}

 

Of course, this is assuming that this target server is set up to accept components. Please ask the server administrator.