cloudfront_asset_host 1.0.0 → 1.0.1

data/README.markdown

@@ -1,21 +1,40 @@
 # CloudFront AssetHost
 
-Easy deployment of your assets on CloudFront or S3. When enabled in production, your assets will be served from Cloudfront/S3 which will result in a speedier front-end.
+Easy deployment of your assets on CloudFront or S3. When enabled in production, your assets will be served from CloudFront/S3 which will result in a speedier front-end.
+
+## Why?
+
+Hosting your assets on CloudFront ensures minimum latency for all your visitors. But deploying your assets requires some additional management that this gem provides.
+
+### Expiration
+
+The best way to expire your assets on CloudFront is to upload the asset to a new unique url. The gem will calculate the MD5-hash of the asset and incorporate that into the URL.
+
+### Efficient uploading
+
+By using the MD5-hash we can easily determined which assets aren't uploaded yet. This speeds up the deployment considerably.
+
+### Compressed assets
+
+CloudFront will not serve compressed assets automatically. To counter this, the gem will upload gzipped javascripts and stylesheets and serve them when the user-agent supports it.
 
 ## Installing
 
-Include the gem in your app's `environment.rb` or Gemfile. It is hosted at Gemcutter[http://gemcutter.org/gems/cloudfront_asset_host]
+    gem install cloudfront_asset_host
+
+Include the gem in your app's `environment.rb` or `Gemfile`.
 
 ### Dependencies
 
+The gem relies on `openssl md5` and `gzip` utilities. Make sure they are available locally and on your servers.
+
+### Configuration
+
 Make sure your s3-credentials are stored in _config/s3.yml_ like this:
 
     access_key_id: 'access_key'
     secret_access_key: 'secret'
 
-The gem relies on +openssl md5+ and +gzip+ utilities. Make sure they are available locally and on your servers.
-
-### Configuration
 Create an initializer to configure the plugin _config/initializers/cloudfront_asset_host.rb_
 
     # Simple configuration
@@ -32,11 +51,11 @@ Create an initializer to configure the plugin _config/initializers/cloudfront_as
       config.s3_config  = "#{RAILS_ROOT}/config/s3.yml" # Alternative location of your s3-config file
 
       # gzip related configuration
-      config.gzip       = true                # enable gzipped assets (defaults to true)
+      config.gzip = true                      # enable gzipped assets (defaults to true)
       config.gzip_extensions = ['js', 'css']  # only gzip javascript or css (defaults to %w(js css))
       config.gzip_prefix = "gz"               # prefix for gzipped bucket (defaults to "gz")
 
-      config.enabled    = true if Rails.env.production? # only enable in production
+      config.enabled = true if Rails.env.production? # only enable in production
     end
 
 ## Usage
@@ -50,6 +69,14 @@ If the plugin is enabled. Rails' internal `asset_host` and `asset_id` functional
 ### Other plugins
 When using in combination with SASS and/or asset_packager it is recommended to generate the css-files and package your assets before uploading them to Cloudfront. For example, call     `Sass::Plugin.update_stylesheets` and `Synthesis::AssetPackage.build_all` first.
 
+## Contributing
+
+Feel free to fork the project and send pull-requests.
+
+## Known Limitations
+
+ - Does not delete old assets
+
 ## Compatibility
 
 Tested on Rails 2.3.5 with SASS and AssetPackager plugins

data/VERSION

@@ -1 +1 @@
-1.0.0
+1.0.1

data/cloudfront_asset_host.gemspec

@@ -5,7 +5,7 @@
 
 Gem::Specification.new do |s|
   s.name = %q{cloudfront_asset_host}
-  s.version = "1.0.0"
+  s.version = "1.0.1"
 
   s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
   s.authors = ["Menno van der Sman"]

metadata

@@ -5,8 +5,8 @@ version: !ruby/object:Gem::Version
   segments: 
   - 1
   - 0
-  - 0
-  version: 1.0.0
+  - 1
+  version: 1.0.1
 platform: ruby
 authors: 
 - Menno van der Sman