AWS Command line tools use AWS_ACCESS_KEY and AWS_SECRET_KEY as environment vars

[combusean]

Shouldn't a utility that uses AWS follow closely to AWS's conventions? I have to keep extra pairs of configuration variables around when deploying stuff and it's hard to keep track of things when there's two different ways of doing things.

[jakelodwick]

+1, sort of.

I had to dig into config.rb to find the expected location of the credentials file:

CONFIG_PATHS = ["#{ENV['S3SYNC_PATH']}", "#{ENV['HOME']}/.s3sync.yml", "/etc/s3sync.yml"]

I would rather just stick them in s3sync.yml in my project's folder (as implied by the existence of s3sync.yml.example in the s3sync repo). Instead, I need to either modify your project's source (not happening) or create a dependency outside my project's folder (also not happening).

Further, configuration should be spelled out in the project's README (which implied that you can just gem install s3sync and get cracking!).

Otherwise, the project looks good, but there's not much encouragement I can offer as I haven't used it yet.