[Capistrano] Re: New to Capistrano... Few fundamental questions

[Jamis Buck]

In deploy.rb, :deploy_to must be set to the directory (on all deployment machines) that you want to contain the deployment directory structure for your app. In other words, if your app is named "flippy", you might set your deploy_to to be "/u/apps/flippy" or "/var/www/flippy". If you run "cap setup", then, capistrano will create the following directory structure *beneath* the directory you specify in deploy_to:

  (deploy_to)/releases
  (deploy_to)/shared
  (deploy_to)/shared/log
  (deploy_to)/shared/system



Does that help?

- Jamis

On Oct 26, 2006, at 11:17 AM, E.B. Farnum wrote:

When you run "cap deploy", it is assumed that this directory structure already exists. Each new release is checked out under (deploy_to)/releases, and then symlinked as (deploy_to)/current.

Great!  Ok, one more question.  Tell me if I'm an idiot.


box and check files in and out of subversion.  I run cap --apply-to.
The path I include on that command is obviously going to be the path
where my rails root is on my dev box.  Is the deploy_to variable in
deploy.rb supposed to point to the place where I already have rails

up because it the root will actually be under the symlinked directory
"current?"

Would the normal way of handling this be just change your config files
around to point at the new rails root?


--~--~---------~--~----~------------~-------~--~----~

So let's say I have a dev box with rails running on it. I work on that installed on my production boxes? If so won't my rails root get messed To unsubscribe from this group, send email to capistrano- [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/ group/capistrano

-~----------~----~----~----~------~----~------~--~---

smime.p7s
Description: S/MIME cryptographic signature