Table of Contents
Kong supports running multiple instances of the Dev Portal with the use of
Workspaces. This allows each Workspace to enable
and maintain separate Dev Portals (complete with separate files, settings, and
authorization) from a within a single instance of Kong.
Managing Multiple Dev Portals within Kong Manager
A snapshot of every Dev Portal within an instance of Kong can be viewed via
the Kong Manager’s Dev Portals top navigation tab.
This overview page details:
- Whether a Dev Portal in a given Workspace is enabled or disabled
- A link to set up the Dev Portal if it is not enabled
- A link to each Dev Portal’s homepage
- A link to each Dev Portal’s indivdual overview page within Kong Manager
- Whether or not each Dev Portal is authenticated (indicated by a lock icon
in the upper right corner of each card)
Enabling a Workspace’s Dev Portal
When a Workspace other than default is created, that Workspace’s Dev Portal
disabled until it is manually enabled.
This can be done from the Kong Manager by clicking the Set up Dev Portal
button located on the Dev Portals Overview page, or by navigating directly
to a Workspace’s Dev Portal Settings page via the sidebar and toggling the
Dev Portal Switch, or by sending the following cURL request:
curl -X PATCH http://localhost:8001/workspaces/<WORKSPACE_NAME> \
On intialization, Kong will populate the new Dev Portal with the Default Settings defined in Kong’s configuration file.
Note A Workspace can only enable a Dev Portal if the Dev Portal feature has been enabled in Kong’s configuration. See Enabling the Dev Portal for more information.
Defining the Dev Portal’s URL structure
The URL of each Dev Portal is automatically configured upon initialization and
is determined by four properties:
- Whether the
portal_gui_use_subdomains property is enabled or disabled
name of the Workspace
Example URL with subdomains disabled:
Example URL with subdomains enabled:
The first three properties are controlled by Kong’s configuration file and
cannot be edited via the Kong Manager.
Overriding Default Settings
On initialization, the Dev Portal will be configured using the Default Portal Settings defined in Kong’s configuration file.
These settings can be manually overriden in the Dev Portals Settings tab
in the Kong Manager or by patching the setting directly.
On initialization of a Workspace’s Dev Portal a copy of the default Dev Portal files will be made and inserted into the new Dev Portal. This allows for the easy transferrence of a customized Dev Portal theme and allows default to act as a ‘master template’ – however the Dev Portal will not continue to sync changes from the default Dev Portal after it is first enabled.
Access is not synced between Dev Portals. If an Admin or Developer would like access to multiple Dev Portals, they must sign up for each Dev Portal individually.