oCIS Single Binary is not responsible for configuring extensions. Instead, each extension could either be configured by environment variables, cli flags or config files.

Each extension has its dedicated documentation page (e.g. which lists all possible configurations. Config files and environment variables are picked up if you use the ./bin/ocis server command within the oCIS single binary. Command line flags must be set explicitly on the extensions subcommands.

Configuration using config files

Out of the box extensions will attempt to read configuration details from:


For this configuration to be picked up, have a look at your extension root command and look for which default config name it has assigned. i.e: onlyoffice reads onlyoffice.json | yaml | toml ....

So far we support the file formats JSON and YAML, if you want to get a full example configuration just take a look at our repository, there you can always see the latest configuration format. These example configurations include all available options and the default values. The configuration file will be automatically loaded if it’s placed at /etc/ocis/ocis.yml, ${HOME}/.ocis/ocis.yml or $(pwd)/config/ocis.yml.

Environment variables

If you prefer to configure the service with environment variables you can see the available variables below.

If multiple variables are listed for one option, they are in order of precedence. This means the leftmost variable will always win if given.

Commandline flags

If you prefer to configure the service with commandline flags you can see the available variables below. Command line flags are only working when calling the subcommand directly.

Root Command

OnlyOffice oCIS extension

Usage: onlyoffice [global options] command [command options] [arguments...]

Path to config file.
Set logging level.
Enable pretty logging.
Enable colored logging.

Sub Commands

onlyoffice health

Check health status

Usage: onlyoffice health [command options] [arguments...]

Address to debug endpoint. Default: flags.OverrideDefaultString(cfg.Debug.Addr, "").

onlyoffice server

Start integrated server

Usage: onlyoffice server [command options] [arguments...]

Enable log to file.
Enable sending traces.
Tracing backend type. Default: flags.OverrideDefaultString(cfg.Tracing.Type, "jaeger").
Endpoint for the agent. Default: flags.OverrideDefaultString(cfg.Tracing.Endpoint, "").
Endpoint for the collector. Default: flags.OverrideDefaultString(cfg.Tracing.Collector, "").
Service name for tracing. Default: flags.OverrideDefaultString(cfg.Tracing.Service, "onlyoffice").
Address to bind debug server. Default: flags.OverrideDefaultString(cfg.Debug.Addr, "").
Token to grant metrics access. Default: flags.OverrideDefaultString(cfg.Debug.Token, "").
Enable pprof debugging.
Enable zpages debugging.
Address to bind http server. Default: flags.OverrideDefaultString(cfg.HTTP.Addr, "").
Set the base namespace for the http namespace. Default: flags.OverrideDefaultString(cfg.HTTP.Namespace, "com.owncloud.web").
Root path of http server. Default: flags.OverrideDefaultString(cfg.HTTP.Root, "/").
Path to custom assets. Default: flags.OverrideDefaultString(cfg.Asset.Path, "").