Skip to content
Qorus Integration Server extension for Visual Studio Code
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.


A developer's front end for Qorus Integration Engine


The extension makes possible remote deployment of edited Qorus source files directly from the VSCode editor.

How to use

Configuration data and corresponding tree view

In order to work with the extension a project must be open in the VSCode editor. By project we mean the root directory of a project (the root of a git repository, for a typical example).

Next, in the root directory there needs to be a project configuration file named qorusproject.json defining development environments and Qorus instances used during the project development. If the configuration file qorusproject.json is not there it can be generated from a template so that the user can simply edit its contents seeing the required structure. Creation of the file is offered in the context menu over each file and each folder within the project.

Based on the configuration file contents a Qorus instances tree view is provided in the explorer pane. Switching to the Qorus instances tree view is done by clicking the hexagon [Q] icon in the activity bar.

More projects (directories) can be open at the same time. When editing alternately files from different projects the Qorus instances tree view changes accordingly.

The configuration file data structure is explained by the following example:

    "qorus_instances": {
        "local": [
                "url": "http://localhost:8001",
                "name": "main local Qorus instance",
                "custom_urls": []
                "url": "https://localhost:8011",
                "name": "local Qorus instance"
        "dev": [
                "url": "",
                "name": "dev 1",
                "custom_urls": [
                        "url": "sftp://abc@def/ghi",
                        "name": "abc"
                        "url": "sftp://xyz@uvw",
                        "name": "xyz"
                "url": "",
                "name": "dev 2"

The interpretation of the data is depicted by a tree with three levels:

  • development environments (here 'local' and 'dev')
    • Qorus instances (here both environments have two Qorus instances)
      • URLs: the Qorus instance "main" URL at the first position and then the custom URLs, if any (here only the 'dev 1' Qorus instance in the 'dev' environment has any custom URLs). Custom URLs are supposed to serve as shortcuts for opening project related sites - simply by clicking (the opening tool depends on the operating system).

The corresponding tree looks as follows:

* local
  * main local Qorus instance
    * main URL (http://localhost:8001)
  * local Qorus instance
    * main URL (https://localhost:8011)
* dev
  * dev 1
    * main URL (
    * abc (sftp://abc@def/ghi)
    * xyz (sftp://xyz@uvw)
  * dev 2
    * main URL (


There are three deployment actions:

  • Deploy the file currently active in the editor. This is executed by the keyboard shortcut Ctrl+Alt+o (or find the command Qorus: Deploy current file in the command box)
  • Deploy a single file from the context menu
  • Deploy a directory from the context menu (deploy all deployable files in the directory including subdirectories)

The deployment is targeted to the Qorus instance that is currently set as active. A Qorus instance can be set as active in the Qorus instances tree view, either from the context menu over a Qorus instance node (second level node) or simply by clicking the Qorus instance node directly. Active Qorus instance is marked by the green light icon. Of course, at most one Qorus instance can be active at a time, setting another instance active inactivates the instance that was active before.


If a Qorus instance requires authentication (and the user has not yet logged in that instance) the Set as active Qorus instance command opens a login dialog and after successful login the instance will be active. Authentication tokens are stored, so next time login is not required. (Tokens are stored only for the VSCode runtime, not persistently.)

The context menus over the Qorus instance tree nodes offer also the following commands

  • Login without setting the instance active
  • Logout (if the instance was active it becomes inactive, of course)
  • Set the instance inactive, but stay logged in
You can’t perform that action at this time.