npm-pipeline-rails 1.6.0 → 1.6.1
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/HISTORY.md +10 -0
- data/README.md +13 -0
- data/lib/npm-pipeline-rails/railtie.rb +6 -2
- data/lib/npm-pipeline-rails/version.rb +1 -1
- metadata +2 -2
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA1:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: b4cf04399ae70cea783c65554533be5c0bfa8567
|
|
4
|
+
data.tar.gz: ac7799a8a5379bc99868f0b90882f5508e00a77d
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: b7c069c95bd71d98c1e3cd89be45d4084bfcce8f3362ad508c09031757613b62f3c8a68b308ba0f337dff36754c268b377851c0e3ba67733f463d3849db9f79e
|
|
7
|
+
data.tar.gz: e29a21e9d22c2886f7ac04ce7c21d1e8fc7444529ddf5949f84107e06d8a1b7089f5d245df52020dd900e0e0c32144bfde3511d92d1d975cadf8c9efcfc48e02
|
data/HISTORY.md
CHANGED
|
@@ -1,3 +1,10 @@
|
|
|
1
|
+
## [v1.6.1]
|
|
2
|
+
> May 27, 2016
|
|
3
|
+
|
|
4
|
+
- [#5] - Fix 'no such process' errors when pressing `^C`. ([#10], [@mikker])
|
|
5
|
+
|
|
6
|
+
[v1.6.1]: https://github.com/rstacruz/npm-pipeline-rails/compare/v1.6.0...v1.6.1
|
|
7
|
+
|
|
1
8
|
## [v1.6.0]
|
|
2
9
|
> May 27, 2016
|
|
3
10
|
|
|
@@ -71,7 +78,10 @@
|
|
|
71
78
|
[#1]: https://github.com/rstacruz/npm-pipeline-rails/issues/1
|
|
72
79
|
[#3]: https://github.com/rstacruz/npm-pipeline-rails/issues/3
|
|
73
80
|
[#4]: https://github.com/rstacruz/npm-pipeline-rails/issues/4
|
|
81
|
+
[#5]: https://github.com/rstacruz/npm-pipeline-rails/issues/5
|
|
74
82
|
[#7]: https://github.com/rstacruz/npm-pipeline-rails/issues/7
|
|
75
83
|
[#9]: https://github.com/rstacruz/npm-pipeline-rails/issues/9
|
|
84
|
+
[#10]: https://github.com/rstacruz/npm-pipeline-rails/issues/10
|
|
76
85
|
[@jasontorres]: https://github.com/jasontorres
|
|
77
86
|
[@victorsolis]: https://github.com/victorsolis
|
|
87
|
+
[@mikker]: https://github.com/mikker
|
data/README.md
CHANGED
|
@@ -72,6 +72,19 @@ You may also want to disable some gems, depending on your set up:
|
|
|
72
72
|
|
|
73
73
|
<br>
|
|
74
74
|
|
|
75
|
+
## Heroku
|
|
76
|
+
|
|
77
|
+
In Heroku, this requires the [Node.js](https://github.com/heroku/heroku-buildpack-nodejs) and [Ruby](https://github.com/heroku/heroku-buildpack-ruby) buildpacks. See: [Using Multiple Buildpacks for an App](https://devcenter.heroku.com/articles/using-multiple-buildpacks-for-an-app) *(devcenter.heroku.com)*
|
|
78
|
+
|
|
79
|
+
```
|
|
80
|
+
heroku buildpacks:set heroku/ruby
|
|
81
|
+
heroku buildpacks:add --index 1 heroku/nodejs
|
|
82
|
+
```
|
|
83
|
+
|
|
84
|
+
Also see [Configuration](#configuration) on how to turn off `config.npm.install_on_asset_precompile`.
|
|
85
|
+
|
|
86
|
+
<br>
|
|
87
|
+
|
|
75
88
|
## Configuration
|
|
76
89
|
|
|
77
90
|
npm-pipeline-rails provides these configuration options:
|
|
@@ -25,8 +25,12 @@ module NpmPipelineRails
|
|
|
25
25
|
|
|
26
26
|
at_exit do
|
|
27
27
|
Utils.log "Terminating '#{name}' [#{pid}]"
|
|
28
|
-
|
|
29
|
-
|
|
28
|
+
begin
|
|
29
|
+
Process.kill 'TERM', pid
|
|
30
|
+
Process.wait pid
|
|
31
|
+
rescue Errno::ESRCH, Errno::ECHILD => e
|
|
32
|
+
Utils.log "'#{name}' [#{pid}] already dead (#{e.class})"
|
|
33
|
+
end
|
|
30
34
|
end
|
|
31
35
|
end
|
|
32
36
|
end
|
metadata
CHANGED
|
@@ -1,14 +1,14 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: npm-pipeline-rails
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version: 1.6.
|
|
4
|
+
version: 1.6.1
|
|
5
5
|
platform: ruby
|
|
6
6
|
authors:
|
|
7
7
|
- Rico Sta. Cruz
|
|
8
8
|
autorequire:
|
|
9
9
|
bindir: exe
|
|
10
10
|
cert_chain: []
|
|
11
|
-
date: 2016-
|
|
11
|
+
date: 2016-09-25 00:00:00.000000000 Z
|
|
12
12
|
dependencies:
|
|
13
13
|
- !ruby/object:Gem::Dependency
|
|
14
14
|
name: railties
|