middleman-aws 1.0.0 → 1.0.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 128306ee099cc7965b6dbfabbffaff57afe0fcee
-  data.tar.gz: 3916fad18988c321d16fa35e2a00f4a81058fd50
+  metadata.gz: 7750b1175743ef7387650a3d4f4563159e9b8317
+  data.tar.gz: bc38b6e7126652c6b67e894fd9973ff6db7a8e6f
 SHA512:
-  metadata.gz: fc5ac87054c46363924561ead0edfdca6af601cdc57a356eb06f561a8c7e61b76821dedc341e13dc175437d0607b73ecf6f16714fde12d3ee4b9b364bb3eb976
-  data.tar.gz: e8c5ce3f8456906bee8243e4a2a799abd89ac48ba124a8e8374fb6a0c2fd52476ac4c02139885acc3487aaae3fff5743390a023b710eee5884367ab578afde75
+  metadata.gz: fc66186d8aa9d340a137e2893d5580487ecaa86784b2bec28c1fcbd45804f45ac688c663f2a08b99dad00f9c8bf5e743098e839794375c128a0821796eacc6ba
+  data.tar.gz: fe4a52e1fe0c51403f2781bfab6a0951f2bf5ad98cdba9e11aab8b8a5e3c2ba6fa75c4fa4adadaff61b39d277443103e8ec9ab22706d8861512f14e68959bdf1

data/README.md

@@ -21,11 +21,12 @@ Simple set of [middleman](http://middlemanapp.com/) rake tasks to build and depl
     gem 'middleman-cloudfront'
 
 
-### Step 3: Add your aws credentials
+### Step 3: AWS credentials
+
+#### Option 1 - secrets file
 e.g. `~/.aws/acme.yml`
 
-This should contain the access and secret keys generated from the selected IAM user.  This is the only file that will need to reside
-outside the repository.  `acme` is equivalent to the directory name for your project.
+This should contain the access and secret keys generated from the selected IAM user.  This is the only file that will need to reside outside the repository.  `acme` is equivalent to the directory name for your project.
 Don't worry, validation will make sure you have the path right.
 
 ```ruby
@@ -33,7 +34,11 @@ access_key_id: XXXXXX
 secret_access_key: XXXXXX
 ```
 
-If you don't create config file, then environment variables `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY` will be used. If there are no such variables, then request to AWS will fail (unless middleman-aws is used on EC2 instance with correct IAM role, then AWS will take care of authorising requests).
+#### Option 2 - ENV variables
+If you don't create secrets file, then environment variables `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY` will be used. 
+
+#### Option 3 - IAM
+If a secrets file is not present (option 1), there are no ENV variables (option 2), then request to AWS will fail (unless middleman-aws is used on EC2 instance with correct IAM role, then AWS will take care of authorising requests).
 
 ### Step 4: Add the necessary s3_sync and Cloudfront sections to your config
 This is a sample of how a common config is setup with variables extracted:

data/lib/middleman-aws/tasks/middleman-aws.rake

@@ -72,7 +72,7 @@ namespace :mm do
     secret_access_key = credentials.fetch('secret_access_key') { ENV['AWS_SECRET_ACCESS_KEY'] }
 
     {
-      access_key_id: access_key_id
+      access_key_id: access_key_id,
       secret_access_key: secret_access_key
     }
   end

data/middleman-aws.gemspec

@@ -3,7 +3,7 @@ $:.push File.expand_path('../lib', __FILE__)
 
 Gem::Specification.new do |s|
   s.name        = 'middleman-aws'
-  s.version     = '1.0.0'
+  s.version     = '1.0.1'
   s.platform    = Gem::Platform::RUBY
 
   s.authors = ['Kevin Ross']

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: middleman-aws
 version: !ruby/object:Gem::Version
-  version: 1.0.0
+  version: 1.0.1
 platform: ruby
 authors:
 - Kevin Ross
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2015-04-16 00:00:00.000000000 Z
+date: 2015-04-18 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: middleman-s3_sync