s3-sync has the ability to receive headers as arguments and pass them to
AWS S3 as metadata headers. This modification proposes to set headers at
configuration so they are written in the objects when deploying.
Main motivation is to be able to pass CacheControl header and have
Cache-Control set for objects ovoiding "Leverage Browser Caching"
throwed by page speed analyzers.
Attention: Metadata are written equal to all objects (files) stored to
S3 and there is no way to tailor it by file type at this moment.
Signed-off-by: Josenivaldo Benito Jr <jrbenito@benito.qsl.br>
Instead of storing sensitive information in your hexo config, you can instead set environment variables for your S3 configuration.
Requires that the environment variables `AWS_KEY` and `AWS_SECRET` be set.
This PR allows someone to define a `region` key in `_config.yml` so that upload works correctly via `s3-sync`.
Why? [`s3-sync`](https://github.com/hughsk/s3-sync) uses [`knox`](https://github.com/LearnBoost/knox) to handle S3 commands. Unless your are uploading to `us-standard`, the upload will fail because the S3 url won't be correct.
