commit 43e1dd6

Merge: b7cd9a5 1fe8b26
Author: Jörn Friedrich Dreyer <jfd@butonic.de>
Date:   Tue Mar 17 17:48:03 2020 +0100

    Merge pull request #148 from owncloud/feature/propagate-config-file

    Make extensions handle their config

getting-started.md

@@ -78,7 +78,21 @@ To the list of available services.
 
 ## Configuration
 
-We provide overall three different variants of configuration. The variant based on environment variables and commandline flags are split up into global values and command-specific values.
+oCIS Single Binary is not responsible for configuring extensions. Instead, each extension could either be configured by environment variables, cli flags or config files.
+
+### Configuration using config files
+
+Out of the box extensions will attempt to read configuration details from:
+
+```console
+/etc/ocis
+$HOME/.ocis
+./config
+```
+
+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: ocis-proxy reads `ocis.json | yaml | toml ...`*.
+
+> Important note: As per the time of this writing, Viper does not play nice with urfave/cli flags, this results in values defined on config files taking precedence over cli flags. This behavior is different with environment variables, these will ALWAYS override any value, as they are the most explicit.
 
 ### Envrionment variables