From 239e1fade70d9784548af54ba0a6eed71e6c685f Mon Sep 17 00:00:00 2001 From: Marco Dickert Date: Thu, 27 Jul 2017 23:25:33 +0200 Subject: [PATCH] Updated Configuration (markdown) --- Configuration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Configuration.md b/Configuration.md index 60287db..77cc354 100644 --- a/Configuration.md +++ b/Configuration.md @@ -24,7 +24,7 @@ The IFM offers the following configuration options. The names depend on wheather | `$config` | env var | description | | :-------- | :------- | :---------- | -| `auth`, `auth_source` | IFM_AUTH | see [authentication](https://github.com/misterunknown/ifm/wiki/Authentication) | +| `auth`, `auth_source` | IFM_AUTH, IFM_AUTH_SOURCE | see [authentication](https://github.com/misterunknown/ifm/wiki/Authentication) | | `root_dir` | IFM_ROOT_DIR | Sets a custom root directory. By default the IFM is locked to its own directory, so you can't go above. Notice that the PHP user has to have sufficient permissions for the `root_dir`, otherwise IFM will not work. Regardless of whether the `root_dir` is set or not, the IFM will **not follow symlinks**, as long as the destination lies outside the `root_dir`. This is by design and cannot be changed. | | `tmp_dir` | IFM_TMP_DIR | Sets a custom temporary directory. This is used to save temporary zip files when you download an entire directory. Make sure the PHP user has write permissions there. | | `ajaxrequest` | IFM_API_AJAXREQUEST | Controls if the user is allowed to perform an ajax request. This was primarily used to debug the IFM in the development process and I didn't remove it since it's quite useful in some cases. |