Rclone config default paths

Could be rclone default config paths extended with

/etc/rclone/rclone.conf ?

Seems a bit counterintuitive as it's a user space program so generally runs as a user.

I just use:

felix@gemini:~$ env | grep RCLONE_CONF

and point it where I want all the time.

You could set that environment variable globally as well and be done with it. No change / feature needed.

I have read about this possibility but storing the config not under the default locations results that the config file has to be specified by --config=""
This induces more typing by running each rclone command.
From my point of view creating a symlink between expected and real path of the config file is a simpler solution.

If you set the environment variable like I shared, you do not have to type it because it's set via the config variable.

rclone ls GD:test -vvv
2022/02/12 11:02:00 DEBUG : Setting --config "/opt/rclone/rclone.conf" from environment variable RCLONE_CONFIG="/opt/rclone/rclone.conf"
2022/02/12 11:02:00 DEBUG : rclone: Version "v1.57.0" starting with parameters ["rclone" "ls" "GD:test" "-vvv"]
2022/02/12 11:02:00 DEBUG : Creating backend with remote "GD:test"
2022/02/12 11:02:00 DEBUG : Using config file from "/opt/rclone/rclone.conf"
2022/02/12 11:02:00 DEBUG : GD: Loaded invalid token from config file - ignoring
2022/02/12 11:02:00 DEBUG : Saving config "token" in section "GD" of the config file
2022/02/12 11:02:00 DEBUG : GD: Saved new token in config file
2022/02/12 11:02:00 DEBUG : Google drive root 'test': 'root_folder_id = 0AGoj85v3xeadUk9PVA' - save this in the config to speed up startup
       -1 testsheet.xlsx
2022/02/12 11:02:00 DEBUG : 6 go routines active

No link or anything needed.

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.