s3_website 2.7.0 → 2.7.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 778dcd186e3206eaf5e03252a3926747dd8d7ba1
-  data.tar.gz: 74dd5fbc8caa9f73115e9fcba347301cf99eeb9d
+  metadata.gz: b16d61f88d92a39c8fd0f0b174ede0244d994aab
+  data.tar.gz: 19f39cde88d46c4a8f7355cdd4bbdebe2e497c89
 SHA512:
-  metadata.gz: 1cd34d83b87621b4cb05204c651a6af6c1fda88e2d7c0edfbfafa9d782217099650d7a3309d48c76b960328c0406f97df530861840a1e57bc10c859b17de5c23
-  data.tar.gz: 0f9260d64f41f661334de67f665b817245d15938abb3582443ab3f2b13915f17927a101c2c1581586196cd47203ef1e9147e54d5ef1fcf9e0ca9161268c4dbbd
+  metadata.gz: 01f0b6b1e80cd8ce4607f945b02b0f2e2375c6edd1ed8ae8d60d0ed5b05b2d1685dda0504f344dc4ee4d54f1e008281e9032101afbd60dffff34f64c50a8104a
+  data.tar.gz: b56e58fd215dfb3c431968c7cb465e51f5fbaff6cd8f3c0a5ddc266fb0e4a23bccaa1e7c030022b983e204f0e4bb582de39f3380a9772b70c18d5988ae090b52

data/.travis.yml

@@ -4,4 +4,4 @@ scala:
 jdk:
   - openjdk6
   - openjdk7
-  - oraclejdk8
+  - oraclejdk8

data/README.md

@@ -219,7 +219,9 @@ create a CloudFront distribution for you.
 If you already have a CloudFront distribution that serves data from your website
 S3 bucket, just add the following line into the file `s3_website.yml`:
 
-    cloudfront_distribution_id: your-dist-id
+```yaml
+cloudfront_distribution_id: your-dist-id
+```
 
 Next time you run `s3_website push`, it will invalidate the items on CloudFront and
 thus force the CDN system to reload the changes from your website S3 bucket.
@@ -254,7 +256,9 @@ You can instruct the push command to invalidate the root resource instead of the
 *index.html* resource by adding the following setting into the configuration
 file:
 
-    cloudfront_invalidate_root: true
+```yaml
+cloudfront_invalidate_root: true
+```
 
 To recap, this setting instructs s3_website to invalidate the root resource
 (e.g., *article/*) instead of the filename'd resource (e.g.,
@@ -318,15 +322,20 @@ command `s3_website cfg apply` internally calls the `configure-s3-website` gem.)
 If your website has a lot of redirects, you may find the following setting
 helpful:
 
-    treat_zero_length_objects_as_redirects: true
+```yaml
+treat_zero_length_objects_as_redirects: true
+```
 
-The setting allows `s3_website push` to infer whether a redirect exists or not.
+The setting allows `s3_website push` to infer whether a redirect exists on the S3 bucket.
 You will experience faster `push` performance when this setting is `true`.
-However, if this setting is enabled and you modify the `redirects` setting in
+
+If this setting is enabled and you modify the `redirects` setting in
 *s3_website.yml*, use `push --force` to apply the modified values.
 
 For backward-compatibility reasons, this setting is `false` by default.
 
+In this context, the word *object* refers to object on S3, not file-system file.
+
 ### Specifying custom concurrency level
 
 By default, `s3_website` does 3 operations in parallel. An operation can be an
@@ -335,7 +344,7 @@ HTTP PUT operation against the S3 API, for example.
 You can increase the concurrency level by adding the following setting into the
 `s3_website.yml` file:
 
-```
+```yaml
 concurrency_level: <integer>
 ```
 
@@ -434,6 +443,7 @@ Contributors (in alphabetical order)
 * Douglas Teoh
 * Greg Karékinian
 * John Allison
+* Jon Frisby
 * Jordan White
 * Justin Latimer
 * László Bácsi

data/changelog.md

@@ -2,6 +2,12 @@
 
 This project uses [Semantic Versioning](http://semver.org).
 
+## 2.7.1
+
+* Loosen dependency requirements
+
+  See <https://github.com/laurilehmijoki/s3_website/pull/135> for discussion.
+
 ## 2.7.0
 
 * Add setting `treat_zero_length_objects_as_redirects`
@@ -12,6 +18,8 @@ This project uses [Semantic Versioning](http://semver.org).
   redirects on your site, you may find that this feature decreases the duration
   of `s3_website push`.
 
+  See <https://github.com/laurilehmijoki/s3_website/issues/132> for discussion.
+
 ## 2.6.1
 
 * Always invalidate the object */index.html* if the setting `cloudfront_invalidate_root` is on

data/lib/s3_website/version.rb

@@ -1,3 +1,3 @@
 module S3Website
-  VERSION = '2.7.0'
+  VERSION = '2.7.1'
 end

data/release

@@ -18,8 +18,7 @@ end
 
 puts "Building s3_website.jar..."
 jar_location = 'target/scala-2.11/s3_website.jar'
-run "./sbt clean"
-run "./sbt assembly"
+run "./sbt clean assembly"
 
 # The bin s3_website uses the MD5 checksum to verify that the jar is not corrupted
 jar_md5 = Digest::MD5.file(jar_location).hexdigest
@@ -33,7 +32,7 @@ run "rake build"
 
 client = Octokit::Client.new(:login => 'laurilehmijoki', :password => ENV['S3_WEBSITE_RELEASE_KEY'])
 release = client.create_release(
-  'laurilehmijoki/s3_website', 
+  'laurilehmijoki/s3_website',
   tag_name,
   :body => "See https://github.com/laurilehmijoki/s3_website/blob/master/changelog.md##{version.gsub('.', '')}"
 )

data/resources/s3_website.jar.md5

@@ -1 +1 @@
-ddc9ee41507905b63f16ab01634e9e5a
+1fd00c96b6f35828bf1a32575f1dffb2

data/s3_website.gemspec

@@ -17,10 +17,10 @@ Gem::Specification.new do |s|
 
   s.default_executable = %q{s3_website}
 
-  s.add_dependency 'thor', '= 0.18.1'
+  s.add_dependency 'thor', '~> 0.18'
   s.add_dependency 'configure-s3-website', '= 1.6.0'
   s.add_dependency 'colored', '1.2'
-  s.add_dependency 'dotenv', '~> 0.11.1'
+  s.add_dependency 'dotenv', '~> 1.0'
 
   s.add_development_dependency 'rake', '10.1.1'
   s.add_development_dependency 'octokit', '3.1.0'

metadata

@@ -1,29 +1,29 @@
 --- !ruby/object:Gem::Specification
 name: s3_website
 version: !ruby/object:Gem::Version
-  version: 2.7.0
+  version: 2.7.1
 platform: ruby
 authors:
 - Lauri Lehmijoki
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2014-11-23 00:00:00.000000000 Z
+date: 2014-11-27 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: thor
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - '='
+    - - "~>"
       - !ruby/object:Gem::Version
-        version: 0.18.1
+        version: '0.18'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - '='
+    - - "~>"
       - !ruby/object:Gem::Version
-        version: 0.18.1
+        version: '0.18'
 - !ruby/object:Gem::Dependency
   name: configure-s3-website
   requirement: !ruby/object:Gem::Requirement
@@ -56,16 +56,16 @@ dependencies:
   name: dotenv
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - ~>
+    - - "~>"
       - !ruby/object:Gem::Version
-        version: 0.11.1
+        version: '1.0'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - ~>
+    - - "~>"
       - !ruby/object:Gem::Version
-        version: 0.11.1
+        version: '1.0'
 - !ruby/object:Gem::Dependency
   name: rake
   requirement: !ruby/object:Gem::Requirement
@@ -103,8 +103,8 @@ executables:
 extensions: []
 extra_rdoc_files: []
 files:
-- .gitignore
-- .travis.yml
+- ".gitignore"
+- ".travis.yml"
 - Gemfile
 - LICENSE
 - README.md
@@ -153,17 +153,17 @@ require_paths:
 - lib
 required_ruby_version: !ruby/object:Gem::Requirement
   requirements:
-  - - '>='
+  - - ">="
     - !ruby/object:Gem::Version
       version: '0'
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
-  - - '>='
+  - - ">="
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 2.2.1
+rubygems_version: 2.2.2
 signing_key: 
 specification_version: 4
 summary: Manage your S3 website