Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Contact Us
  • Home
  • Settings
  • Extensions

Deploying Extensions to the DryvIQ Platform

Learn how to deploy extensions to your DryvIQ Platform.

Written by Andrea Harvey

Updated at May 5th, 2025

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Insights
    Prebuilt Insights Custom Insights
  • Content
  • Accounts
  • Activity Log
  • Content Scans
  • Migrations
    Migration Jobs Migration Reports Maps Flagged Items Migration Tools
  • Connections
    Supported Platform Connections Creating Connections Connection Maintenance Connection Pools
  • Entity Types
    DryvIQ Available Entity Types Custom Entity Types Entity Type Maintenance
  • Action Sets
    Creating Action Sets Action Sets Maintenance
  • Settings
    License Performance Notifications Extensions Entity Types Settings Display Settings Configuration
  • API, CLI, and SDK Documentation
    REST API Documentation Command-line Interface SDK Development
  • POC Offering
  • Release Notes
+ More

Table of Contents

Overview Deploying the Extension with DryvIQ Deploying the Extension to an Existing DryvIQ Instance

Overview

During development of this extension, it is recommended to build the extension using dotnet build, which will build your extension in the Debug configuration as well as copy the extension into the appropriate directory on your machine for DryvIQ to pick it up if you have a local copy that you can use to test live within the product. However, once you are ready to deploy this extension to customers, you will want to package it as a NuGet package (.nupkg file) using dotnet pack --configuration Release and deploy it to a DryvIQ instance. This guide assumes you have a NuGet package you want to deploy.

Deploying the Extension with DryvIQ 

The DryvIQ installer supports deploying custom extensions alongside the normal DryvIQ installation process. To do this, an extension developer would create an extensions.zip file that contains all NuGet packages (.nupkg files) that should be deployed alongside DryvIQ.

This method of deployment is not supported when deploying to a Docker container. When using Docker to deploy DryvIQ, you must use the method below to install the extension to an existing DryvIQ instance.

 

Deploying the Extension to an Existing DryvIQ Instance

DryvIQ also supports installing custom extensions into an existing DryvIQ instance. This process is the same regardless of whether you have a single-node or a multi-node cluster. Once DryvIQ is installed and the database is configured, you can install the extension using several methods.

Before deploying the extensions, verify that an Extensions folder does not exist in the Installation Directory. The default directory is C:\Program Files\SkySync, but it can be changed during installation. If the folder exists in this directory, delete it before running the command to install the extensions.

 

To deploy an extension to an offline instance, meaning that the DryvIQ instance is not actively running, you can use the following command:

skysync extensions deploy MyCustomExtension.nupkg

This will install the extension into the DryvIQ database to be installed and deployed on each node in the cluster once the instances are brought online.

You can also deploy an extension into a running DryvIQ instance using the skysync-cli or the REST interface. To use the CLI, ensure you have the CLI installed and configured before continuing.

skysync-cli extensions add MyCustomExtension.nupkg

Once the extension is installed, any nodes that were previously running will need to be restarted for the new extension to take effect. Do not use the Restart button in the Settings or an API to restart the service since these options perform a soft restart needed to pick up changes to the appsettings.json file. A full restart of the service is required when installing extensions. 

 

 

extensions dotnet nuget

Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • Network File System
  • LDAP Account and Group Maps Using REST API
  • Connection Management Using REST API

Copyright 2025 – DryvIQ.

Knowledge Base Software powered by Helpjuice

Expand