rails_external_asset_pipeline 0.1.0 → 0.2.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 316fb38e35719f17288367d71ef42998d7672f25
-  data.tar.gz: 2562d4d3ef5d073463d87ccb6060ce79c3c03c14
+  metadata.gz: 1a638e36ede2466a8e61d0aaeef99d76b8ae1675
+  data.tar.gz: c6071f9ebd34e3abe91afe2a247cacba584b5b2a
 SHA512:
-  metadata.gz: 77601b11f160da63a9af5b4d5f29d81666a787bc74616486bd8d00d2a53fbbda33047d38f55dafce6838b0488b9de632d22cc1c03ada291b80b037938157a401
-  data.tar.gz: c01ebd79a52326fa588f20073a9e2407797d3d6a28aa6be20cac91f803c32e0456e679a2f098748f8b1089309f3ae0529a58e2610d905f38f2a726f2273e6eb2
+  metadata.gz: ae2ed1c58638b1ed7d1e85d02d429dd64c8b9153fac69efb64d45cdd3c2fe297fedd63bb1980ff9dfbc1c285207b3fb8cc3441b88db4ba9ab35761d1b157f654
+  data.tar.gz: 509b9c120189d32f40e4abf104445ee1069700a265bb7875fbe4622c3f6d5e756f6563399854f85304902e19fee4ff0044a42b613480c0feffd2912d318c94f5

data/README.md

@@ -4,7 +4,7 @@ Instead of using the built-in asset pipeline of Rails, some people want to use e
 
 Why is an integration like that required? If your external asset pipeline modifies the names of the generated files depending on their content (for example by adding a hash of the file to the name), Rails will not be able to find the files on its own. You still want to be able to use the helpers you are used to like `stylesheet_link_tag` or `image_tag`, and they should put out the correct URL for the desired asset. This technique is referred to as *cache busting*.
 
-So let's say you have a JavaScript file called `application.js` (for example in `app/assets/javascripts`) and your external asset pipeline generates a file called `application-03118e77692b637cfc0f55bb27fef087.js` (for example in `public/assets/javascripts`) from that file. When you use `stylesheet_link_tag 'application'`, you expect that the resulting HTML points to the file containing the hash in its filename. To do that, your pipeline needs to generate manifest files for each type of asset. In this case, it needs to generate a file called `javascript.json` in `public/assets/manifests`. The file should look like this:
+So let's say you have a JavaScript file called `application.js` (for example in `app/assets/javascripts`) and your external asset pipeline generates a file called `application-03118e77692b637cfc0f55bb27fef087.js` (for example in `public/assets/javascripts`) from that file. When you use `stylesheet_link_tag 'application'`, you expect that the resulting HTML points to the file containing the hash in its filename. To do that, your pipeline needs to generate manifest files for each type of asset. In this case, it needs to generate a file called `javascript.json` in `public/assets/manifests` (to change this, see the Configuration section). The file should look like this:
 
 ```json
 {
@@ -25,7 +25,6 @@ The types supported by this gem are:
 * `stylesheet`
 * `javascript`
 * `image`
-* `font`
 
 You can find an example of using this gem in Rails 5 with an external Node.js pipeline [here](https://github.com/moonglum/rails-5-and-node-asset-pipeline).
 
@@ -49,6 +48,16 @@ Or install it yourself as:
 $ gem install rails_external_asset_pipeline
 ```
 
+## Configuration
+
+By default this gem assumes that your manifest files can be found in `public/assets/manifests`. You can change that with the following configuration:
+
+```ruby
+config.x.rails_external_asset_pipeline.manifests_path = File.join("my", "own", "manifests", "path")
+```
+
+The `manifests_path` is relative to your Rails Root.
+
 ## Development
 
 After checking out the repo, run `bin/setup` to install dependencies. You can also run `bin/console` for an interactive prompt that will allow you to experiment.

data/lib/rails_external_asset_pipeline/compute_asset_path.rb

@@ -6,11 +6,16 @@ module RailsExternalAssetPipeline
 
     def compute_asset_path(source, options = {})
       if TYPES_WITH_MANIFEST.include? options[:type]
-        manifest = Manifest.new(options[:type])
+        manifest = Manifest.new(manifests_path, options[:type])
         manifest.fetch(source)
       else
         source
       end
     end
+
+    def manifests_path
+      Rails.configuration.x.rails_external_asset_pipeline.manifests_path ||
+        File.join("public", "assets", "manifests")
+    end
   end
 end

data/lib/rails_external_asset_pipeline/manifest.rb

@@ -1,6 +1,7 @@
 module RailsExternalAssetPipeline
   class Manifest
-    def initialize(type)
+    def initialize(manifests_path, type)
+      @manifests_path = manifests_path
       @type = type
     end
 
@@ -15,21 +16,21 @@ module RailsExternalAssetPipeline
     def parsed_manifest
       JSON.parse(unparsed_manifest)
     rescue JSON::ParserError
-      raise "The manifest file '#{asset_path}' is invalid JSON"
+      raise "The manifest file '#{manifest_path}' is invalid JSON"
     end
 
     def unparsed_manifest
-      File.read(full_asset_path)
+      File.read(full_manifest_path)
     rescue Errno::ENOENT
-      raise "The manifest file '#{asset_path}' is missing"
+      raise "The manifest file '#{manifest_path}' is missing"
     end
 
-    def full_asset_path
-      File.join(Rails.root, asset_path)
+    def full_manifest_path
+      File.join(Rails.root, manifest_path)
     end
 
-    def asset_path
-      File.join("public", "assets", "manifests", "#{@type}.json")
+    def manifest_path
+      File.join(@manifests_path, "#{@type}.json")
     end
   end
 end

data/lib/rails_external_asset_pipeline/version.rb

@@ -1,3 +1,3 @@
 module RailsExternalAssetPipeline
-  VERSION = "0.1.0"
+  VERSION = "0.2.0"
 end

metadata

@@ -1,29 +1,29 @@
 --- !ruby/object:Gem::Specification
 name: rails_external_asset_pipeline
 version: !ruby/object:Gem::Version
-  version: 0.1.0
+  version: 0.2.0
 platform: ruby
 authors:
 - Lucas Dohmen
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2016-07-22 00:00:00.000000000 Z
+date: 2016-08-09 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rails
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - "~>"
+    - - ">="
       - !ruby/object:Gem::Version
-        version: 5.0.0
+        version: 4.2.6
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - "~>"
+    - - ">="
       - !ruby/object:Gem::Version
-        version: 5.0.0
+        version: 4.2.6
 - !ruby/object:Gem::Dependency
   name: rubocop
   requirement: !ruby/object:Gem::Requirement
@@ -38,6 +38,20 @@ dependencies:
     - - "~>"
       - !ruby/object:Gem::Version
         version: 0.41.2
+- !ruby/object:Gem::Dependency
+  name: rake
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 11.2.2
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 11.2.2
 description: Instead of using the build-inn asset pipeline of Rails, some people want
   to use external asset pipelines – written in Node.js for example. This gem enables
   the required integration with Rails.