Rails%203%20In%20Action

Deploy away!
Figure 14.2 Paste in the key, and add a title.
If there is a ticketee directory at the current location of the server that contains the
directories your application should contain, then this works. You can delete this
directory now; you’ll be putting the code on the server at another location using
Capistrano.
Before that happens, you’ll need to configure Capistrano.
14.5.2 Configuring Capistrano
To begin with, add the capistrano gem to your application’s Gemfile using this code:
group :development do
gem 'capistrano'
end
To install this gem, you (and other developers of your application) are able to run
bundle install, which will keep those other developers up-to-date with all gems. Running
gem install capistrano would only update them with Capistrano, and even
then it may be a version that is incompatible with the one that you’ve developed.
When the gem is installed, you can set it up inside a Rails application by running
this command from the root of the application:
capify .
This will create two files: Capfile and config/deploy.rb. The Capfile is a file containing
setup for Capistrano in the application and the following default code that will be
used to load your Capistrano configuration:
load 'deploy' if respond_to?(:namespace) # cap2 differentiator
Dir['vendor/plugins/*/recipes/*.rb'].each { |plugin| load(plugin) }
load 'config/deploy' # remove this line to skip loading any ...
397