s3_website_monadic 0.0.1

data/features/cassettes/cucumber_tags/s3-and-cloudfront.yml

@@ -0,0 +1,290 @@
+---
+http_interactions:
+- request:
+    method: get
+    uri: https://s3.amazonaws.com/
+    body:
+      encoding: US-ASCII
+      string: ''
+    headers:
+      Content-Type:
+      - ''
+      User-Agent:
+      - aws-sdk-ruby/1.5.6 ruby/1.9.3 x86_64-darwin11.4.0
+      Date:
+      - Sun, 14 Oct 2012 17:19:58 +0300
+      Authorization:
+      - AWS
+      Accept:
+      - ! '*/*'
+  response:
+    status:
+      code: 200
+      message: OK
+    headers:
+      X-Amz-Id-2:
+      - XVTH5v7I60Us5NH8Zkjqe+hJt2pZSJufKVDZYyeWa64s44hHkHpniCmXgOwpTz44
+      X-Amz-Request-Id:
+      - 814A58953B2F1408
+      Date:
+      - Sun, 14 Oct 2012 14:20:00 GMT
+      Content-Type:
+      - application/xml
+      Transfer-Encoding:
+      - chunked
+      Server:
+      - AmazonS3
+    body:
+      encoding: US-ASCII
+      string: ! '<?xml version="1.0" encoding="UTF-8"?>
+
+        <ListAllMyBucketsResult xmlns="http://s3.amazonaws.com/doc/2006-03-01/"><Owner><ID></ID><DisplayName></DisplayName></Owner><Buckets><Bucket><Name>s3-website-test.net</Name><CreationDate>2012-10-14T12:58:37.000Z</CreationDate></Bucket></Buckets></ListAllMyBucketsResult>'
+    http_version:
+  recorded_at: Sun, 14 Oct 2012 14:19:59 GMT
+- request:
+    method: get
+    uri: https://s3.amazonaws.com/s3-website-test.net?max-keys=1000
+    body:
+      encoding: US-ASCII
+      string: ''
+    headers:
+      Content-Type:
+      - ''
+      User-Agent:
+      - aws-sdk-ruby/1.5.6 ruby/1.9.3 x86_64-darwin11.4.0
+      Date:
+      - Sun, 14 Oct 2012 17:19:59 +0300
+      Authorization:
+      - AWS
+      Accept:
+      - ! '*/*'
+  response:
+    status:
+      code: 200
+      message: OK
+    headers:
+      X-Amz-Id-2:
+      - kqI8qY2X6hz6gn5LkBZ5ucppTQAnEtwB/WUxm3Mpp5IP9maZEOrudhkrnSZ50L8Z
+      X-Amz-Request-Id:
+      - AA070701525DE2D7
+      Date:
+      - Sun, 14 Oct 2012 14:20:03 GMT
+      Content-Type:
+      - application/xml
+      Transfer-Encoding:
+      - chunked
+      Server:
+      - AmazonS3
+    body:
+      encoding: US-ASCII
+      string: ! '<?xml version="1.0" encoding="UTF-8"?>
+
+        <ListBucketResult xmlns="http://s3.amazonaws.com/doc/2006-03-01/"><Name>s3-website-test.net</Name><Prefix></Prefix><Marker></Marker><MaxKeys>1000</MaxKeys><IsTruncated>false</IsTruncated></ListBucketResult>'
+    http_version:
+  recorded_at: Sun, 14 Oct 2012 14:20:01 GMT
+- request:
+    method: put
+    uri: https://s3.amazonaws.com/s3-website-test.net/css/styles.css
+    body:
+      encoding: ASCII-8BIT
+      string: !binary |-
+        Ym9keSB7Cgp9Cg==
+    headers:
+      Content-Type:
+      - ''
+      Content-Length:
+      - '10'
+      User-Agent:
+      - aws-sdk-ruby/1.5.6 ruby/1.9.3 x86_64-darwin11.4.0
+      Date:
+      - Sun, 14 Oct 2012 17:20:01 +0300
+      Authorization:
+      - AWS
+      Accept:
+      - ! '*/*'
+  response:
+    status:
+      code: 200
+      message: OK
+    headers:
+      X-Amz-Id-2:
+      - yiJ0xvPzssJs1/qbY1JtU4eCcrCb7RoGKmCubzT66JE2f97jBRCh/GrDGQbhzBE0
+      X-Amz-Request-Id:
+      - A48B2F4C626AA36F
+      Date:
+      - Sun, 14 Oct 2012 14:20:04 GMT
+      Etag:
+      - ! '"8fcf43a38cbf0c502f029a50645f2374"'
+      Content-Length:
+      - '0'
+      Server:
+      - AmazonS3
+    body:
+      encoding: US-ASCII
+      string: ''
+    http_version:
+  recorded_at: Sun, 14 Oct 2012 14:20:02 GMT
+- request:
+    method: put
+    uri: https://s3.amazonaws.com/s3-website-test.net/index.html
+    body:
+      encoding: ASCII-8BIT
+      string: !binary |-
+        PGh0bWw+CiAgPGhlYWQ+CiAgICA8dGl0bGU+aGVsbG8hPC90aXRsZT4KICA8
+        L2hlYWQ+CjwvaHRtbD4K
+    headers:
+      Content-Type:
+      - ''
+      Content-Length:
+      - '60'
+      User-Agent:
+      - aws-sdk-ruby/1.5.6 ruby/1.9.3 x86_64-darwin11.4.0
+      Date:
+      - Sun, 14 Oct 2012 17:20:02 +0300
+      Authorization:
+      - AWS
+      Accept:
+      - ! '*/*'
+  response:
+    status:
+      code: 200
+      message: OK
+    headers:
+      X-Amz-Id-2:
+      - jB6/sj8qczNX7hdyr0BxlkN4hbv3ztad+qTDnC6b9XY580AcWSCMKMr2j5AzB/TR
+      X-Amz-Request-Id:
+      - 9EDF08D87D4C7EA2
+      Date:
+      - Sun, 14 Oct 2012 14:20:04 GMT
+      Etag:
+      - ! '"8a8892a2b0fad281f26c0dedbff7011a"'
+      Content-Length:
+      - '0'
+      Server:
+      - AmazonS3
+    body:
+      encoding: US-ASCII
+      string: ''
+    http_version:
+  recorded_at: Sun, 14 Oct 2012 14:20:03 GMT
+- request:
+    method: get
+    uri: https://s3.amazonaws.com/s3-website-test.net?max-keys=1000
+    body:
+      encoding: US-ASCII
+      string: ''
+    headers:
+      Content-Type:
+      - ''
+      User-Agent:
+      - aws-sdk-ruby/1.5.6 ruby/1.9.3 x86_64-darwin11.4.0
+      Date:
+      - Sun, 14 Oct 2012 17:20:03 +0300
+      Authorization:
+      - AWS
+      Accept:
+      - ! '*/*'
+  response:
+    status:
+      code: 200
+      message: OK
+    headers:
+      X-Amz-Id-2:
+      - 28rS+qE332bAH7P5X4xCZSTKfk41Aa8+8coL6JykVGWgook8UwngNCs+vdp+MUjU
+      X-Amz-Request-Id:
+      - FE954A121529EA60
+      Date:
+      - Sun, 14 Oct 2012 14:20:05 GMT
+      Content-Type:
+      - application/xml
+      Transfer-Encoding:
+      - chunked
+      Server:
+      - AmazonS3
+    body:
+      encoding: US-ASCII
+      string: ! '<?xml version="1.0" encoding="UTF-8"?>
+
+        <ListBucketResult xmlns="http://s3.amazonaws.com/doc/2006-03-01/"><Name>s3-website-test.net</Name><Prefix></Prefix><Marker></Marker><MaxKeys>1000</MaxKeys><IsTruncated>false</IsTruncated><Contents><Key>css/styles.css</Key><LastModified>2012-10-14T14:20:04.000Z</LastModified><ETag>&quot;8fcf43a38cbf0c502f029a50645f2374&quot;</ETag><Size>10</Size><Owner><ID>3855ebae0f370c3dd0c8d8031863792112bd2a2cb18fa310d3f463ae0dea62f1</ID><DisplayName>fluid83</DisplayName></Owner><StorageClass>STANDARD</StorageClass></Contents><Contents><Key>index.html</Key><LastModified>2012-10-14T14:20:04.000Z</LastModified><ETag>&quot;8a8892a2b0fad281f26c0dedbff7011a&quot;</ETag><Size>60</Size><Owner><ID>3855ebae0f370c3dd0c8d8031863792112bd2a2cb18fa310d3f463ae0dea62f1</ID><DisplayName>fluid83</DisplayName></Owner><StorageClass>STANDARD</StorageClass></Contents></ListBucketResult>'
+    http_version:
+  recorded_at: Sun, 14 Oct 2012 14:20:03 GMT
+- request:
+    method: get
+    uri: https://s3.amazonaws.com/s3-website-test.net?max-keys=1000
+    body:
+      encoding: US-ASCII
+      string: ''
+    headers:
+      Content-Type:
+      - ''
+      User-Agent:
+      - aws-sdk-ruby/1.5.6 ruby/1.9.3 x86_64-darwin11.4.0
+      Date:
+      - Sun, 14 Oct 2012 17:20:03 +0300
+      Authorization:
+      - AWS
+      Accept:
+      - ! '*/*'
+  response:
+    status:
+      code: 200
+      message: OK
+    headers:
+      X-Amz-Id-2:
+      - H8PnL8xdXT/f8NBPuBRM20MoNP3GXwCurPtToM9xm1xRz8dSWhvmZRz5gtbHLEaS
+      X-Amz-Request-Id:
+      - A88E10E350D2ABBF
+      Date:
+      - Sun, 14 Oct 2012 14:20:05 GMT
+      Content-Type:
+      - application/xml
+      Transfer-Encoding:
+      - chunked
+      Server:
+      - AmazonS3
+    body:
+      encoding: US-ASCII
+      string: ! '<?xml version="1.0" encoding="UTF-8"?>
+
+        <ListBucketResult xmlns="http://s3.amazonaws.com/doc/2006-03-01/"><Name>s3-website-test.net</Name><Prefix></Prefix><Marker></Marker><MaxKeys>1000</MaxKeys><IsTruncated>false</IsTruncated><Contents><Key>css/styles.css</Key><LastModified>2012-10-14T14:20:04.000Z</LastModified><ETag>&quot;8fcf43a38cbf0c502f029a50645f2374&quot;</ETag><Size>10</Size><Owner><ID>3855ebae0f370c3dd0c8d8031863792112bd2a2cb18fa310d3f463ae0dea62f1</ID><DisplayName>fluid83</DisplayName></Owner><StorageClass>STANDARD</StorageClass></Contents><Contents><Key>index.html</Key><LastModified>2012-10-14T14:20:04.000Z</LastModified><ETag>&quot;8a8892a2b0fad281f26c0dedbff7011a&quot;</ETag><Size>60</Size><Owner><ID>3855ebae0f370c3dd0c8d8031863792112bd2a2cb18fa310d3f463ae0dea62f1</ID><DisplayName>fluid83</DisplayName></Owner><StorageClass>STANDARD</StorageClass></Contents></ListBucketResult>'
+    http_version:
+  recorded_at: Sun, 14 Oct 2012 14:20:04 GMT
+- request:
+    method: post
+    uri: https://cloudfront.amazonaws.com/2012-05-05/distribution/foo/invalidation
+    body:
+      encoding: US-ASCII
+      string: ! "\n        <InvalidationBatch>\n          <Paths>\n            <Quantity>2</Quantity>\n
+        \           <Items>\n              [\"<Path>/css/styles.css</Path>\", \"<Path>/index.html</Path>\"]\n
+        \           </Items>\n          </Paths>\n          <CallerReference>1350224404</CallerReference>\n
+        \       </InvalidationBatch>\n      "
+    headers:
+      X-Amz-Date:
+      - Sun, 14 Oct 2012 17:20:04 EEST
+      Content-Type:
+      - text/xml
+      Authorization:
+      - AWS
+  response:
+    status:
+      code: 201
+      message: Created
+    headers:
+      X-Amzn-Requestid:
+      - 402b2709-160a-11e2-8263-5718d272b82f
+      Location:
+      - https://cloudfront.amazonaws.com/2012-05-05/distribution/foo/invalidation/I29QRGBBZOGEZ9
+      Content-Type:
+      - text/xml
+      Content-Length:
+      - '394'
+      Date:
+      - Sun, 14 Oct 2012 14:20:06 GMT
+    body:
+      encoding: US-ASCII
+      string: ! '<?xml version="1.0"?>
+
+        <Invalidation xmlns="http://cloudfront.amazonaws.com/doc/2012-05-05/"><Id>I29QRGBBZOGEZ9</Id><Status>InProgress</Status><CreateTime>2012-10-14T14:20:05.839Z</CreateTime><InvalidationBatch><Paths><Quantity>2</Quantity><Items><Path>/index.html</Path><Path>/css/styles.css</Path></Items></Paths><CallerReference>1350224404</CallerReference></InvalidationBatch></Invalidation>'
+    http_version:
+  recorded_at: Sun, 14 Oct 2012 14:20:05 GMT
+recorded_with: VCR 2.2.4

data/features/cloudfront.feature

@@ -0,0 +1,54 @@
+Feature: Invalidate the Cloudfront distribution
+
+  In order to publish my posts
+  As a blogger who delivers his blog via an S3-based Cloudfront distribution
+  I want to run s3_website
+  And see, that the items in the distribution were invalidated
+  So that my latest updates will be immediately available to readers
+
+  @s3-and-cloudfront
+  Scenario: Upload to S3 and then invalidate the Cloudfront distribution
+    When my S3 website is in "features/support/test_site_dirs/cdn-powered.blog.fi"
+    And I call the push command
+    Then the output should contain
+      """
+      Invalidating Cloudfront items...
+        /
+      succeeded
+      """
+
+  @s3-and-cloudfront-when-updating-a-file
+  Scenario: Update a blog entry and then upload
+    When my S3 website is in "features/support/test_site_dirs/cdn-powered.with-one-change.blog.fi"
+    And I call the push command
+    Then the output should equal
+      """
+      Deploying features/support/test_site_dirs/cdn-powered.with-one-change.blog.fi/_site/* to s3-website-test.net
+      Calculating diff ... done
+      Uploading 1 changed file(s)
+      Upload index.html: Success!
+      Done! Go visit: http://s3-website-test.net.s3-website-us-east-1.amazonaws.com/index.html
+      Invalidating Cloudfront items...
+        /index.html
+        /
+      succeeded
+
+      """
+
+  @s3-and-cloudfront-after-deleting-a-file
+  Scenario: Delete a blog post and then push the website
+    When my S3 website is in "features/support/test_site_dirs/cdn-powered.when-deleted-a-file.blog.fi"
+    And I call the push command
+    Then the output should equal
+      """
+      Deploying features/support/test_site_dirs/cdn-powered.when-deleted-a-file.blog.fi/_site/* to s3-website-test.net
+      Calculating diff ... done
+      No new or changed files to upload
+      Delete css/styles.css: Success!
+      Done! Go visit: http://s3-website-test.net.s3-website-us-east-1.amazonaws.com/index.html
+      Invalidating Cloudfront items...
+        /css/styles.css
+        /
+      succeeded
+
+      """

data/features/command-line-help.feature

@@ -0,0 +1,54 @@
+Feature: displaying help text in the command-line interface
+
+  As a user
+  I want to see the available commands and options right on CLI
+  So that I don't have to browse the documentation on the web
+
+  @starts-new-os-process
+  Scenario: User wants to know what he can do with s3_website
+    When I run `s3_website`
+    Then the output should contain:
+      """
+      Commands:
+        s3_website cfg SUBCOMMAND ...ARGS  # Operate on the config file
+        s3_website help [COMMAND]          # Describe available commands or one spe...
+        s3_website push                    # Push local files with the S3 website
+      """
+
+  @starts-new-os-process
+  Scenario: User wants to know what the push command does
+    When I run `s3_website help push`
+    Then the output should contain:
+      """
+      Usage:
+        s3_website push
+      """
+
+  @starts-new-os-process
+  Scenario: User wants to know what the cfg command does
+    When I run `s3_website cfg`
+    Then the output should contain:
+      """
+      Commands:
+        s3_website cfg apply           # Apply the configuration on the AWS services
+        s3_website cfg create          # Create a config file with placeholder values
+        s3_website cfg help [COMMAND]  # Describe subcommands or one specific subco...
+      """
+
+  @starts-new-os-process
+  Scenario: User wants to know what the cfg apply command does
+    When I run `s3_website cfg help apply`
+    Then the output should contain:
+      """
+      Usage:
+        s3_website apply
+      """
+
+  @starts-new-os-process
+  Scenario: User wants to know what the cfg create command does
+    When I run `s3_website cfg help create`
+    Then the output should contain:
+      """
+      Usage:
+        s3_website create
+      """

data/features/delete.feature

@@ -0,0 +1,19 @@
+Feature: remove an S3 website page from S3
+
+  In order to remove a webpage from S3
+  As a blogger
+  I want to run s3_website and see that my webpage was deleted from S3
+
+  @one-file-to-delete
+  Scenario: The user deletes a blog post
+    When my S3 website is in "features/support/test_site_dirs/unpublish-a-post.com"
+    And I call the push command
+    Then the output should equal
+      """
+      Deploying features/support/test_site_dirs/unpublish-a-post.com/_site/* to s3-website-test.net
+      Calculating diff ... done
+      No new or changed files to upload
+      Delete index.html: Success!
+      Done! Go visit: http://s3-website-test.net.s3-website-us-east-1.amazonaws.com/index.html
+
+      """

data/features/error_reporting.feature

@@ -0,0 +1,24 @@
+Feature: reporting errors to the user
+
+  Background: we want to show a non-technical error report to the user.
+    Consequently, we do not print the stack trace of the error.
+
+  @starts-new-os-process
+  @network-io
+  Scenario: The user calls "push" when the S3 credentials are invalid
+    When I run `s3_website push --site ../../features/support/test_site_dirs/my.blog.com --config_dir ../../features/support/test_site_dirs/my.blog.com`
+    Then the output should contain:
+      """
+      The AWS Access Key Id you provided does not exist in our records. (AWS::S3::Errors::InvalidAccessKeyId)
+      """
+    And the output should not contain:
+      """
+      throw
+      """
+    And the exit status should be 1
+
+  @starts-new-os-process
+  @network-io
+  Scenario: The user calls "cfg apply" when the S3 credentials are invalid
+    When I run `s3_website cfg apply`
+    And the exit status should be 1

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

@@ -0,0 +1,154 @@
+Feature: Instructions for a new user
+
+  As a new s3_website user
+  I would like to get helpful feedback when running `s3_website`
+  So that I can upload my S3 website to S3 without headache
+
+  @starts-new-os-process
+  Scenario: Run s3_website in the wrong directory
+    When I run `s3_website push`
+    Then the output should contain:
+      """
+      I can't find a website in any of the following directories: public/output, _site. Please specify the location of the website with the --site option.
+      """
+
+  @starts-new-os-process
+  Scenario: Configuration is incomplete
+    When I run `s3_website push`
+    Then the exit status should be 1
+
+  @starts-new-os-process
+  Scenario: Create placeholder config file
+    Given a directory named "_site"
+    When I run `s3_website cfg create`
+    Then the output should contain:
+      """
+      I've just generated a file called s3_website.yml. Go put your details in it!
+      """
+    Then the file "s3_website.yml" should contain:
+      """
+      s3_id: YOUR_AWS_S3_ACCESS_KEY_ID
+      s3_secret: YOUR_AWS_S3_SECRET_ACCESS_KEY
+      s3_bucket: your.blog.bucket.com
+      """
+
+  @starts-new-os-process
+  Scenario: Run s3_website push for the first time
+    Given a directory named "_site"
+    When I run `s3_website push`
+    Then the output should contain:
+      """
+      I've just generated a file called s3_website.yml. Go put your details in it!
+      """
+    Then the file "s3_website.yml" should contain:
+      """
+      s3_id: YOUR_AWS_S3_ACCESS_KEY_ID
+      s3_secret: YOUR_AWS_S3_SECRET_ACCESS_KEY
+      s3_bucket: your.blog.bucket.com
+      """
+
+  @starts-new-os-process
+  Scenario: Run s3_website with an empty configuration file
+    Given a directory named "_site"
+    And an empty file named "s3_website.yml"
+    When I run `s3_website push`
+    Then the output should contain:
+      """
+      I can't parse the file s3_website.yml. It should look like this:
+      s3_id: YOUR_AWS_S3_ACCESS_KEY_ID
+      s3_secret: YOUR_AWS_S3_SECRET_ACCESS_KEY
+      s3_bucket: your.blog.bucket.com
+      """
+
+  @starts-new-os-process
+  Scenario: The user wants to know the available configurations by looking at the cfg file
+    Given a directory named "_site"
+    When I run `s3_website push`
+    Then the file "s3_website.yml" should contain:
+      """
+      # max_age:
+      """
+    Then the file "s3_website.yml" should contain:
+      """
+      # gzip:
+      """
+    Then the file "s3_website.yml" should contain:
+      """
+      # s3_endpoint:
+      """
+    Then the file "s3_website.yml" should contain:
+      """
+      # ignore_on_server:
+      """
+    Then the file "s3_website.yml" should contain:
+      """
+      # s3_reduced_redundancy:
+      """
+    Then the file "s3_website.yml" should contain:
+      """
+      # cloudfront_distribution_id:
+      """
+    Then the file "s3_website.yml" should contain:
+      """
+      # cloudfront_distribution_config:
+      """
+    Then the file "s3_website.yml" should contain:
+      """
+      # redirects:
+      """
+    Then the file "s3_website.yml" should contain:
+      """
+      # routing_rules:
+      """
+    Then the file "s3_website.yml" should contain:
+      """
+      # concurrency_level:
+      """
+    Then the file "s3_website.yml" should contain:
+      """
+      # extensionless_mime_type: text/html
+      """
+
+  @starts-new-os-process
+  Scenario: Run s3_website with a malformed configuration file
+    Given a directory named "_site"
+    And a file named "s3_website.yml" with:
+      """
+      s3_id: YOUR_AWS_S3_ACCESS_KEY_ID
+      this is not yaml
+      """
+    When I run `s3_website push`
+    Then the output should contain:
+      """
+      I can't parse the file s3_website.yml. It should look like this:
+      s3_id: YOUR_AWS_S3_ACCESS_KEY_ID
+      s3_secret: YOUR_AWS_S3_SECRET_ACCESS_KEY
+      s3_bucket: your.blog.bucket.com
+      """
+
+  @starts-new-os-process
+  Scenario: Run s3_website with a configuration file that does not contain a bucket
+    Given a directory named "_site"
+    And a file named "s3_website.yml" with:
+      """
+      s3_id: YOUR_AWS_S3_ACCESS_KEY_ID
+      s3_secret: YOUR_AWS_S3_SECRET_ACCESS_KEY
+      s3_bucket:
+      """
+    When I run `s3_website push`
+    Then the output should contain:
+      """
+      I can't parse the file s3_website.yml. It should look like this:
+      s3_id: YOUR_AWS_S3_ACCESS_KEY_ID
+      s3_secret: YOUR_AWS_S3_SECRET_ACCESS_KEY
+      s3_bucket: your.blog.bucket.com
+      """
+
+  @new-files
+  Scenario: Print the URL of the to the user
+    When my S3 website is in "features/support/test_site_dirs/my.blog.com"
+    And I call the push command
+    Then the output should contain
+      """
+      Go visit: http://s3-website-test.net.s3-website-us-east-1.amazonaws.com/index.html
+      """

data/features/jekyll-support.feature

@@ -0,0 +1,20 @@
+Feature: upload a Jekyll site
+
+  @new-files
+  Scenario: Push a Jekyll site to S3
+    When my S3 website is in "features/support/test_site_dirs/jekyllrb.com"
+    And I call the push command
+    Then the output should contain
+      """
+      Deploying features/support/test_site_dirs/jekyllrb.com/_site/* to s3-website-test.net
+      Calculating diff ... done
+      Uploading 2 new file(s)
+      """
+    And the output should contain
+      """
+      Upload css/styles.css: Success!
+      """
+    And the output should contain
+      """
+      Upload index.html: Success!
+      """

data/features/nanoc-support.feature

@@ -0,0 +1,20 @@
+Feature: upload a Nanoc site
+
+  @new-files
+  Scenario: Push a Nanoc site to S3
+    When my S3 website is in "features/support/test_site_dirs/nanoc.ws"
+    And I call the push command
+    Then the output should contain
+      """
+      Deploying features/support/test_site_dirs/nanoc.ws/public/output/* to s3-website-test.net
+      Calculating diff ... done
+      Uploading 2 new file(s)
+      """
+    And the output should contain
+      """
+      Upload css/styles.css: Success!
+      """
+    And the output should contain
+      """
+      Upload index.html: Success!
+      """