Ignore config.yml in deployment or leave private

[kmjungersen]

Hello! First, thanks for a great utility - it's been really helpful so far! Currently I'm manually making config.yml private in my S3 bucket so that the AWS access keys aren't made public with the rest of the site. It'd be nice if they were already made private on deploy.

If I have some free time, I'll put together a PR for this, but wanted to open the issue for discussion first. Thanks!

[Irishsmurf]

It might be an idea to pull the credentials from the default AWS CLI/SDK credential file location - in the ~/.aws directory, rather than using a separate config.yml file specific for the application.

[kmjungersen]

+1 to that

[ottenhoff]

+1 ... I was surprised to find my access keys being published.

[lacostenycoder]

+1 seeing as how I'm using S3 to host a static website, uploading the config file is a pretty big security issue. Yikes.

[Eein]

A wild PR appears. :)