Rails%203%20In%20Action

Deploy away!
The next line after this makes these folders group writable with the chmod
command:
chmod g+w /home/ticketeeapp.com/apps/ticketee
/home/ticketeeapp.com/apps/ticketee/releases
/home/ticketeeapp.com/apps/ticketee/shared
/home/ticketeeapp.com/apps/ticketee/shared/system
/home/ticketeeapp.com/apps/ticketee/shared/log
/home/ticketeeapp.com/apps/ticketee/shared/pids
At the bottom of this command’s output you can see what servers it will be executed
on, with only your one server listed for now. It also tells you that the command is being
executed and, faster than you can blink, that the command has finished. chmod isn’t
an intensive operation:
servers: ["your-server"]
[your-server] executing command
command finished
Once the deploy:setup Capistrano task has finished, you are returned to a console
prompt. Now you can put the application on the server by deploying it!
14.5.4 Deploying the application
Capistrano has now been configured to deploy the Ticketee application and you’ve
set up your server using the cap deploy:setup command, leaving it up to you now to
deploy your code. Capistrano’s deploy task will let you do this, and you can run this
task with this command:
cap deploy
This command outputs an even larger output to cap deploy:setup, but again we’ll go
through it line by line. It’s not all that intimidating when it’s broken down into little
chunks, really! The first output you’ll see from a deploy is
* executing `deploy'
* executing `deploy:update'
** transaction: start
* executing `deploy:update_code'
These first three lines tell you the tasks which are being executed. The deploy task is
going to be executed because you asked Capistrano to do that. This task depends on
the deploy:update task, and so it will run that first.
The deploy:update task begins a transaction (the third line in the output), which
is exceptionally helpful. If anything goes wrong in your deploy, Capistrano will roll
back everything to the beginning of this transaction, deleting any code it’s deployed.
This transaction is a failsafe for your deploy.
The final part of the output is the deploy:update_code task, which is responsible
for updating the application’s code in your deployment environment. This task is
responsible for the next chunk of output you see:
401