Edit configuration

To edit a configuration, click the edit button on the far right. The configuration settings expand and can be edited. The following options are available.

  • Enabled Select to show the application in the user portal.
  • Display name Name as shown in the user portal.
  • Application Slug Part of the URL that is unique for this application.
  • Log traffic Select to log traffic.
  • Front-end version override Applications define a front-end version, usually a production build of the same version used during development. This can be overriden here.
  • Authorized groups Restrict access to the application to groups of users. Leave empty for unrestricted access.
  • Application owner Name of the application owner.
  • Application owner email Email address of the application owner.
  • Description Description of the application shown in the user portal.
  • Documentation URL Link to documentation pages.
  • Back-end type Discussed in the section below.

Back-end type

Currently, the following back-end types are available:

Each back-end type has some specific settings, that will be discussed in the relevant sub-sections.

The back-end settings are grouped in three categories:

  • cURL options PHP curl_setopt options, see cURL options.
  • Cache Settings for connecting to a REDIS database that can cache the session state, see Cache.
  • Certificate Settings for HTTPS connections, see Certificate.
  • Application data Key value pairs that can be provided to the application during initialization, see Application data.

Python ownR

The Python ownR configuration has one specific setting that is not part of the above mentioned categories:

  • function_name The ownR entry point function.