Extensions are under development because of the beta badge 1 stage of Infinite Scale. Their service, environment variables and configuration may change. Forgive us if there are mistakes or information is missing. Feel free to report issues and we’ll take care of them as soon as possible on github. You want to fix them yourself? We’d appreciate that even more.

Table of Contents


Extensions are microservices and core components of Infinite Scale. Each extension serves a particular task and can be configured independently. Extensions started with the runtime share the runtime management while extensions running outside the runtime are managed on their own but connect to each other when necessary.

For more details see Managing Extensions.

There are descriptions and configuration details for each extension available.

General Information

Multiple environment variables for the same purpose

You may see in the tables describing the environment variables that there are two environment variables in the same row configuring the same task. In such a case, the following rule applies:

  • The first environment variable is used on a global scale. If set, it will be used in all extensions where applicable.

  • The second environment variable overwrites the first one, but ONLY for the one particular extension.

Taking the webdav extension as an example, you want to set the OCIS_URL as a generic value, but for webdav, you want to use a different URL defined with OCIS_PUBLIC_URL.

Extension name vs. environment variable name

Environment variable names are always upper case and words are connected with an underscore. They start with the name of the extension. If the extension name is more than one word and the words are connected with a dash, the dash is replaced by an underscore. This info is useful when you search for environment variables based on the extension name.

Example: auth-basicAUTH_BASIC_XXX

Default values containing curly brackets

In the table showing the environment variables of an extension, the Default Value cell can sometimes contain values with curly brackets like {{.Id.OpaqueId}}. These are valid default values.