s3_website 1.1.0 → 1.1.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: de54cc1b98c305031806e7486cfb3c4e62027db1
-  data.tar.gz: 4d95bafa1686532d6e3c8223418694b8699b2ad0
+  metadata.gz: fea6e88850680b95f753e74ff1a12402e6670483
+  data.tar.gz: c02c9ddf15d4b6df65803b31bfc33161fc3bb24f
 SHA512:
-  metadata.gz: 45905b400e8439f0040d180d051066407beccb219870a9ea68077c6a2bdbb1e78a5dbfb2cdbc8d5472ebc4db3c04c83751f27b37e0e341713033c5d0e8674b6a
-  data.tar.gz: a49e6beb52409c4ee47fa620efa540c5014a320f67ec518231d0632ca97fcf8e23f19fcc5f9a9d706f3dc71baa2c0ae1d8e9a4f083427b1a415b22b06c1d828b
+  metadata.gz: 503d48ed49c1b6411a56f4be61dbd1372ec9768c74069a03f2559e65a65e6e55eb6ee0288040b00162e138a9d221f11d875dd69637ece9057a07d1e459a58e32
+  data.tar.gz: b7a2522205f751d20735883e1255db641e3dd0299251195806538056379dfceb9a8be6255c2596e0b68b692004c18d31e106a1f82aa18d197e5f0f62b4ba000a

data/changelog.md

@@ -2,6 +2,10 @@
 
 This project uses [Semantic Versioning](http://semver.org).
 
+## 1.1.1
+
+* Mention the new `concurrency_level` setting in the sample config file
+
 ## 1.1.0
 
 * Add possibility to define the concurrency level in *s3_website.yml*

data/example-configurations.md

@@ -19,7 +19,9 @@ s3_bucket: your.domain.net
 If you run `s3_website` on an EC2 instance with IAM roles, it is possible to omit
 the `s3_id` and `s3_secret`.
 
-## Optimised for speed: using CloudFront, gzip and cache headers
+## Optimised for speed
+
+Use CloudFront, gzip, cache headers and greater concurrency:
 
 ````yaml
 s3_id: <%= ENV['your_domain_net_aws_key'] %>
@@ -35,6 +37,7 @@ cloudfront_distribution_config:
       CNAME: your.domain.net
 max_age: 120
 gzip: true
+concurrency_level: 100
 ````
 
 Above, we store the AWS credentials and the id of the CloudFront distribution as

data/features/instructions-for-new-user.feature

@@ -95,6 +95,10 @@ Feature: Instructions for a new user
       """
       # routing_rules:
       """
+    Then the file "s3_website.yml" should contain:
+      """
+      # concurrency_level:
+      """
 
   @starts-new-os-process
   Scenario: Run s3_website with a malformed configuration file

data/resources/configuration_file_template.yml

@@ -30,6 +30,8 @@ s3_bucket: your.blog.bucket.com
 #     items:
 #       CNAME: your.website.com
 
+# concurrency_level: 100
+
 # redirects:
 #   index.php: /
 #   about.php: about.html

data/s3_website.gemspec

@@ -3,7 +3,7 @@ $:.push File.expand_path("../lib", __FILE__)
 
 Gem::Specification.new do |s|
   s.name        = "s3_website"
-  s.version     = "1.1.0"
+  s.version     = "1.1.1"
   s.platform    = Gem::Platform::RUBY
   s.authors     = ["Lauri Lehmijoki"]
   s.email       = ["lauri.lehmijoki@iki.fi"]

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: s3_website
 version: !ruby/object:Gem::Version
-  version: 1.1.0
+  version: 1.1.1
 platform: ruby
 authors:
 - Lauri Lehmijoki
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2013-07-20 00:00:00.000000000 Z
+date: 2013-07-21 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: aws-sdk