Add or manage External Instance
Register another Nodinite environment once, and export configuration to it directly whenever you need to.
- ✅ Name each target environment so exports pick the right one
- ✅ Point at the target's Web API for direct connectivity
- ✅ Edit or delete a registration when an environment moves or retires
An External Instance is another instance of Nodinite, used as a target for Export. To add one, open Administration › Settings › External Instances in the Web Client and click Add External Instance. To edit one, click its name in the External Instances overview or use the Action button.
Important
The Import / Export feature is disabled in Nodinite 7.0; until it returns, exports don't use External Instances. Use the Web API to move data between instances.
Instructions
Name and URI are required; Save and close returns you to the list.
Name
A Name is required to create the External Instance. Use the environment name, for example Production, so it is easy to pick in the export wizard.
Description
Adding a Description is optional.
URI
URI stands for Uniform Resource Identifier and is the link to the Web API of the External Instance, without /api.
Example: https://servername:40001/ (in Nodinite 7 the Web API runs at the root of its own web site). Use the host and port of the external environment's Web API; they come from that environment's settings in the Nodinite Portal (Servers step).
Note
The screenshot shows the older example
http://servername/Nodinite/WebAPIunder the field. That is the Nodinite 6 address format; use the v7 format above.
Access requirements
The target Web API must be reachable from the source environment, and the user who runs the export must be a member of the built-in Administrators Role in both environments.