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

Add the capistrano v3 way of using gateway servers

Browse source 
This is based on the discussion in
https://github.com/capistrano/capistrano/issues/725#issuecomment-30089068
and there is also the git config way of doing it.
This commit is contained in:
Filipe Giusti 2013-12-13 03:57:24 -02:00
parent d5452de2be
commit 0c1c93ed09
2 changed files with 30 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
documentation/getting-started/authentication-and-authorisation/index.markdown
View file

@ -160,6 +160,22 @@ href="https://twitter.com/postmodern_mod3/statuses/300438256200339456">February
<script async src="//platform.twitter.com/widgets.js"
charset="utf-8"></script>
If your server isn't accessible directly and you need to use the SSH
ProxyCommand option, you should do
{% prism ruby %}
require 'net/ssh/proxy/command'
set :ssh_options, proxy: Net::SSH::Proxy::Command.new('ssh mygateway.com -W %h:%p')
# OR
server 'internal-hostname',
ssh_options: {
proxy: Net::SSH::Proxy::Command.new('ssh mygateway.com -W %h:%p'),
}
{% endprism %}
#### 1.2 From our servers to the repository host
With access from workstations to the servers settled, there is another hop to

17
documentation/upgrading/index.markdown
View file

@ -33,6 +33,17 @@ layout: default
Update `config/deploy/production.rb` and `config/deploy/staging.rb` to have relevant data there. You may also want to add more stages from old configs (`old_cap/deploy/`).
5.
If you had a gateway server set doing `set :gateway, "www.capify.org"` you should upgrade to
{% prism ruby %}
require 'net/ssh/proxy/command'
set :ssh_options, proxy: Net::SSH::Proxy::Command.new('ssh mygateway.com -W %h:%p')
{% endprism %}
Or the per-server `ssh_options` equivalent.
6.
Now you need to refactor your old `deploy.rb` (also `Capfile`, but in most of cases developers didn't change it in Capistrano 2.x). Move parameters (like `set :deploy_to, "/home/deploy/#{application}"` or `set :keep_releases, 4`) to `config/deploy.rb` and tasks to `Capfile`.
*Important: `repository` option was renamed to `repo_url`.*
@ -40,7 +51,7 @@ layout: default
Notice that some parameters are not necessary anymore: `use_sudo`, `normalize_asset_timestamps`.
6.
7.
If you didn't use `deploy_to` before and deployed to `/u/apps/your_app_name`, you need one more change. Now default deploy path is `/var/www/app_name` and your config will be broken after upgrade. Just declare custom `deploy_to` option:
{% prism ruby %}
@ -49,10 +60,10 @@ layout: default
But in advance, `/u/apps` is not the best place to store apps and we advice you to change it later.
7.
8.
Keep editing Capfile and uncomment addons you need, such as rbenv/rvm, bundler or rails.
8.
9.
Yay! Try to deploy with your new config set. If you discover any missing info in this upgrade guide, you're welcome to contribute to it.
# General recommendations