capistrano-faster-rails 1.0.0 → 1.0.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 267f8d4165d2dfd5a34f51ee33ab376057ee609b8ea3d18db05b4138a657b078
-  data.tar.gz: 0267eb20da80f65880cce0189cae1e7fb0df4a1192f307558091e944cc78e6a4
+  metadata.gz: 9c2c3730d3b927436497b333a98319aaf7d629d683e8c6fe59c116a8eff18bcb
+  data.tar.gz: c848c81e5bcd3836a7ba184c83666b41124c43c4a9e1eeebbde317ad68dc6616
 SHA512:
-  metadata.gz: be5dca1f91d6a8df868d167b37f9dc899920e2c90b8682a92ef3d67177d912528780827fdfb5ab2a408e597f172173a98adf90d42d68b5b44a40d98332faa383
-  data.tar.gz: 780b849843a81098dad49205f4986fd9921eafd17699da96aa2a07bbc28c2cc095af4277e2bebc6f229a585514ea044b1fc5a623a5d0cfd24d1994b686dfcb54
+  metadata.gz: db51f5f8b561eca96d5eca0ff786b29cb7b301db26dbc61ea3fb0e9bf875a18ffe52ebb56da6770a8a5ffb25cdc90365c06ef5d4fcfb8694a48250d3bdb82908
+  data.tar.gz: 6f0eb89c9151ee1d01f50e5dbe49b6af957722c6028ceb1142913555e876da5b6ce5465ca099d8d343992999f6003e8416a11ebd42aa81ffc19af4db7035e91f

data/capistrano-faster-rails.gemspec

@@ -4,15 +4,22 @@ $LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
 
 Gem::Specification.new do |spec|
   spec.name          = "capistrano-faster-rails"
-  spec.version       = "1.0.0"
+  spec.version       = "1.0.1"
   spec.authors       = ["lifuzhong"]
   spec.email         = ["lifuzho@126.com"]
 
   spec.summary       = %q{Speedup deploy Ruby On Rails project when using capistrano}
   spec.description   = %q{
-    1. Capistrano runs each command separately on their own SSH session and that's why it takes so long to deploy an application, copy `linked_files` and `linked_dirs` with one command will speedup deploying process.
-    2. `bundle install` takes few or dozens of seconds. generally, you don't have to execute `bundle install` if your Gemfile and Gemfile.lock not changed
-    3. `rake assets:precompile` is really slow if your Rails project has plenty of assets to precompile, even if they are not changed. You don't have to precompile them if not chagned.
+    What does this gem do?
+
+      1. Execute copy `linked_files` and `linked_dirs` with one command on deployed servers.
+      Capistrano runs each command separately on their own SSH session and it takes too long to deploy an application, copy `linked_files` and `linked_dirs` on deployed servers with one command will speedup deploying process.
+
+      2. Skip `bundle install` if Gemfile isn't changed.
+      `bundle install` takes few or dozens of seconds, most of the time your project's Gemfile will not be changed, and you don't have to execute `bundle install` if your Gemfile isn't changed.
+
+      3. Skip `rake assets:precompile` if asset files not chagned.
+      `rake assets:precompile` is really slow if your Rails project has plenty of assets to precompile, even if they are not changed. You don't have to execute `rake assets:precompile` if your asset files not chagned.
   }
   spec.homepage      = "https://github.com/ifool/capistrano-faster-rails"
   spec.license       = 'MIT'

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: capistrano-faster-rails
 version: !ruby/object:Gem::Version
-  version: 1.0.0
+  version: 1.0.1
 platform: ruby
 authors:
 - lifuzhong
@@ -38,13 +38,17 @@ dependencies:
     - - "~>"
       - !ruby/object:Gem::Version
         version: '10.0'
-description: "\n    1. Capistrano runs each command separately on their own SSH session
-  and that's why it takes so long to deploy an application, copy `linked_files` and
-  `linked_dirs` with one command will speedup deploying process.\n    2. `bundle install`
-  takes few or dozens of seconds. generally, you don't have to execute `bundle install`
-  if your Gemfile and Gemfile.lock not changed\n    3. `rake assets:precompile` is
-  really slow if your Rails project has plenty of assets to precompile, even if they
-  are not changed. You don't have to precompile them if not chagned.\n  "
+description: "\n    What does this gem do?\n\n      1. Execute copy `linked_files`
+  and `linked_dirs` with one command on deployed servers.\n      Capistrano runs each
+  command separately on their own SSH session and it takes too long to deploy an application,
+  copy `linked_files` and `linked_dirs` on deployed servers with one command will
+  speedup deploying process.\n\n      2. Skip `bundle install` if Gemfile isn't changed.\n
+  \     `bundle install` takes few or dozens of seconds, most of the time your project's
+  Gemfile will not be changed, and you don't have to execute `bundle install` if your
+  Gemfile isn't changed.\n\n      3. Skip `rake assets:precompile` if asset files
+  not chagned.\n      `rake assets:precompile` is really slow if your Rails project
+  has plenty of assets to precompile, even if they are not changed. You don't have
+  to execute `rake assets:precompile` if your asset files not chagned.\n  "
 email:
 - lifuzho@126.com
 executables: []