middleman-aws 1.0.0 → 1.0.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +4 -4
- data/README.md +9 -4
- data/lib/middleman-aws/tasks/middleman-aws.rake +1 -1
- data/middleman-aws.gemspec +1 -1
- metadata +2 -2
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA1:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: 7750b1175743ef7387650a3d4f4563159e9b8317
|
4
|
+
data.tar.gz: bc38b6e7126652c6b67e894fd9973ff6db7a8e6f
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: fc66186d8aa9d340a137e2893d5580487ecaa86784b2bec28c1fcbd45804f45ac688c663f2a08b99dad00f9c8bf5e743098e839794375c128a0821796eacc6ba
|
7
|
+
data.tar.gz: fe4a52e1fe0c51403f2781bfab6a0951f2bf5ad98cdba9e11aab8b8a5e3c2ba6fa75c4fa4adadaff61b39d277443103e8ec9ab22706d8861512f14e68959bdf1
|
data/README.md
CHANGED
@@ -21,11 +21,12 @@ Simple set of [middleman](http://middlemanapp.com/) rake tasks to build and depl
|
|
21
21
|
gem 'middleman-cloudfront'
|
22
22
|
|
23
23
|
|
24
|
-
### Step 3:
|
24
|
+
### Step 3: AWS credentials
|
25
|
+
|
26
|
+
#### Option 1 - secrets file
|
25
27
|
e.g. `~/.aws/acme.yml`
|
26
28
|
|
27
|
-
This should contain the access and secret keys generated from the selected IAM user. This is the only file that will need to reside
|
28
|
-
outside the repository. `acme` is equivalent to the directory name for your project.
|
29
|
+
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.
|
29
30
|
Don't worry, validation will make sure you have the path right.
|
30
31
|
|
31
32
|
```ruby
|
@@ -33,7 +34,11 @@ access_key_id: XXXXXX
|
|
33
34
|
secret_access_key: XXXXXX
|
34
35
|
```
|
35
36
|
|
36
|
-
|
37
|
+
#### Option 2 - ENV variables
|
38
|
+
If you don't create secrets file, then environment variables `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY` will be used.
|
39
|
+
|
40
|
+
#### Option 3 - IAM
|
41
|
+
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).
|
37
42
|
|
38
43
|
### Step 4: Add the necessary s3_sync and Cloudfront sections to your config
|
39
44
|
This is a sample of how a common config is setup with variables extracted:
|
data/middleman-aws.gemspec
CHANGED
metadata
CHANGED
@@ -1,14 +1,14 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: middleman-aws
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 1.0.
|
4
|
+
version: 1.0.1
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- Kevin Ross
|
8
8
|
autorequire:
|
9
9
|
bindir: bin
|
10
10
|
cert_chain: []
|
11
|
-
date: 2015-04-
|
11
|
+
date: 2015-04-18 00:00:00.000000000 Z
|
12
12
|
dependencies:
|
13
13
|
- !ruby/object:Gem::Dependency
|
14
14
|
name: middleman-s3_sync
|