Allow configuration in yml file

[bep]

Allow configuration in yml file

[bep]

Yes, we should fix that. I suspect this is a case of me adding config file support "after the fact".

[bep]

Thinking about this.

bucket: example.com
key: xcsds
region: us-east-2
secret: xdsfdsf
source: public

I don't think key/secret should be in this file, as it this file should be committed to GitHub, secrets should .... stay secret.

[Jos512]

I don't think key/secret should be in this file, as it this file should be committed to GitHub, secrets should .... stay secret.

Sure for GitHub. But those that use private BitBucket repositories, like me, can safely commit the key and secret in the config file. Perhaps we can add a warning about this in the README file?

[bep]

Perhaps we can add a warning about this in the README file?

Yes, OK, that would be good. I guess there are plenty of ways a user can shoot him/herself in the foot.