1
0
Fork 0
mirror of https://github.com/capistrano/capistrano synced 2023-03-27 23:21:18 -04:00

Generated changes from my latest tweaks, and those from Huming Teo

This commit is contained in:
Lee Hambley 2013-07-09 09:50:20 +02:00
parent 106f705736
commit 642a5c76ec
3 changed files with 8 additions and 8 deletions

View file

@ -140,7 +140,7 @@ the Rails community to pick and choose support for components they use
surrounding environmental issues around PTY vs non-TTY environments, login
and non-login shells not to mention <em>environment managers</em> such as rvm,
rbenv and nvm.</li>
<li><strong>Speed.</strong> We know that in a lot of environments speed of deploment is a
<li><strong>Speed.</strong> We know that in a lot of environments speed of deployment is a
huge factor, since Rails introduced the <em>Asset Pipeline</em> it&#39;s not uncommon
for a deploy that formerly took 5 seconds now takes 5 minutes. This really
is mostly out of our control, but with improved support for parallelism,
@ -383,7 +383,7 @@ both connections.</p>
</blockquote>
<p>This cleanup routine can now be better implemented as follows (which is
actually more or less the actual implenetation in the the new Gem):</p>
actually more or less the actual implementation in the the new Gem):</p>
<div>
<pre data-line=''><code class='language-ruby'># Capistrano 3.0.x
@ -727,7 +727,7 @@ the Rails community to pick and choose support for components they use
surrounding environmental issues around PTY vs non-TTY environments, login
and non-login shells not to mention <em>environment managers</em> such as rvm,
rbenv and nvm.</li>
<li><strong>Speed.</strong> We know that in a lot of environments speed of deploment is a
<li><strong>Speed.</strong> We know that in a lot of environments speed of deployment is a
huge factor, since Rails introduced the <em>Asset Pipeline</em> it&#39;s not uncommon
for a deploy that formerly took 5 seconds now takes 5 minutes. This really
is mostly out of our control, but with improved support for parallelism,
@ -970,7 +970,7 @@ both connections.</p>
</blockquote>
<p>This cleanup routine can now be better implemented as follows (which is
actually more or less the actual implenetation in the the new Gem):</p>
actually more or less the actual implementation in the the new Gem):</p>
<div>
<pre data-line=''><code class='language-ruby'># Capistrano 3.0.x

View file

@ -205,7 +205,7 @@ role :db, %w{example.com}
# ======================
# This can be used to drop a more detailed server
# definition into the server list. The second argument
# something that quacks like a has can be used to set
# something that quacks like a hash can be used to set
# extended properties on the server.
server &#39;example.com&#39;, roles: %w{web app}, my_property: :my_value
@ -397,7 +397,7 @@ role :db, %w{example.com}
# ======================
# This can be used to drop a more detailed server
# definition into the server list. The second argument
# something that quacks like a has can be used to set
# something that quacks like a hash can be used to set
# extended properties on the server.
server &#39;example.com&#39;, roles: %w{web app}, my_property: :my_value

View file

@ -107,7 +107,7 @@
<h3 id="toc_0">A Simple Task</h3>
<div>
<pre data-line=''><code class='language-ruby'>role :demo, %w{example.com example.org, example.net}
<pre data-line=''><code class='language-ruby'>role :demo, %w{example.com example.org example.net}
task :uptime do |host|
on roles(:demo), in: :parallel do
uptime = capture(:uptime)
@ -147,7 +147,7 @@ extended to support them.</p>
<!-- <h3 id="toc_0">A Simple Task</h3>
<div>
<pre data-line=''><code class='language-ruby'>role :demo, %w{example.com example.org, example.net}
<pre data-line=''><code class='language-ruby'>role :demo, %w{example.com example.org example.net}
task :uptime do |host|
on roles(:demo), in: :parallel do
uptime = capture(:uptime)