github/rclone
1
Fork 0
mirror of https://github.com/rclone/rclone synced 2024-10-16 01:41:12 +02:00
Code Releases Activity

docs: add section about config variable precedence

Browse Source 
See: https://forum.rclone.org/t/precedence-rules-for-config/17707
This commit is contained in:
Nick Craig-Wood 2020-07-07 11:12:35 +01:00
parent b2f4f52b64
commit 0f72aa8a5f
1 changed files with 21 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
docs/content/docs.md
View File

@ -1849,6 +1849,27 @@ mys3:
Note that if you want to create a remote using environment variables
you must create the `..._TYPE` variable as above.
### Precedence
The various different methods of backend configuration are read in
this order and the first one with a value is used.
- Flag values as supplied on the command line, eg `--drive-use-trash`.
- Remote specific environment vars, eg `RCLONE_CONFIG_MYREMOTE_USE_TRASH` (see above).
- Backend specific environment vars, eg `RCLONE_DRIVE_USE_TRASH`.
- Config file, eg `use_trash = false`.
- Default values, eg `true` - these can't be changed.
So if both `--drive-use-trash` is supplied on the config line and an
environment variable `RCLONE_DRIVE_USE_TRASH` is set, the command line
flag will take preference.
For non backend configuration the order is as follows:
- Flag values as supplied on the command line, eg `--stats 5s`.
- Environment vars, eg `RCLONE_STATS=5s`.
- Default values, eg `1m` - these can't be changed.
### Other environment variables ###
- `RCLONE_CONFIG_PASS` set to contain your config file password (see [Configuration Encryption](#configuration-encryption) section)