Which cloud storage system are you using? (eg Google Drive)
N/A
The command you were trying to run (eg rclone copy /tmp remote:tmp)
I ran config/create from the RPC interface to login to my account, and found that the config got stored at ~/.config/rclone/rclone.config. I have the RCLONE_CONFIG environment variable set to ~/.config/{my-program-name}/rclone.config though, and it's thus appearing that setting RCLONE_CONFIG is having no effect.
I just followed the instructions for building the C library that are shown here, and attempting to run the following code appears to always load the config from ~/.config/rclone/rclonf.config, even if RCLONE_CONFIG is set:
Sorry for the late reply, I got busy with some stuff and didn't get a chance to really look into this until now.
Anyway your change makes everything work correctly - is there any reason the environment variable method wouldn't work instead here though? I'm just thinking about potentially wanting to use other CLI flags in the future, and being able to set those via environment variables would be quite convenient
You can set this on a global basis, or on a local (per command) basis.
--config is missing from that list along with a small number of flags like --retries and --stats (you are expected to do your own high level retries via the API).
It should be a complete list!
You can see the options with rclone rc --loopback options/get
I didn't think about that either, I completely forgot seeing that the other day, and that probably would solve pretty much anything I need. I can see how --config would be the exception in this case - there's no specific flags I was needing set, it was more of a mindset of thinking about potential future needs (though none have been present yet).
I think the way that branch handles things is fine then, I'm fine with getting that into the codebase as soon as you are