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

Changes to support easier deployment, and the generated docs

Browse source
This commit is contained in:
Lee Hambley 2013-09-19 13:21:25 +02:00
parent 3ac989cb78
commit b5e7afd99c
2 changed files with 7 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
_site/Rakefile
View file

@ -6,7 +6,7 @@ release_timestamp = Time.now.utc.strftime("%Y%m%d%H%m%S")
desc "Build Jekyll Site And Sync With S3"
task :deploy do
sh "jekyll build"
sh "bundle exec jekyll build"
on 'harrow.io' do
upload! '_site/', deploy_to, recursive: true
within(deploy_to) do

8
_site/documentation/getting-started/authentication-and-authorisation/index.html
View file

@ -155,7 +155,9 @@ could contribute a Windows guide to this, so we can include it here.</p>
<p>An SSH key is a mechanism that allows a <em>public</em> half one key to be placed on
a server, when we want to authenticate with that server, our SSH client uses
the <strong>private</strong> part of that key to negotiate with the server, if the keys are
correct, then we need to create the key.</p>
correct, we are allowed to login.</p>
<p>Then we need to create the key.</p>
<p><strong>Hint:</strong> If you have more than one developer in your team, they should all add their
public key to the <code>deploy</code> user&#39;s <code>authorized_keys</code> file, that way if someone
@ -515,7 +517,9 @@ could contribute a Windows guide to this, so we can include it here.</p>
<p>An SSH key is a mechanism that allows a <em>public</em> half one key to be placed on
a server, when we want to authenticate with that server, our SSH client uses
the <strong>private</strong> part of that key to negotiate with the server, if the keys are
correct, then we need to create the key.</p>
correct, we are allowed to login.</p>
<p>Then we need to create the key.</p>
<p><strong>Hint:</strong> If you have more than one developer in your team, they should all add their
public key to the <code>deploy</code> user&#39;s <code>authorized_keys</code> file, that way if someone