release_path is recomputed every time Capistrano is invoked, and is only valid for a deploy that is IN PROGRESS.
current_path, on the other hand, always points to the 'current' symlink. current_release is always the most recent release in the releases directory. Lastly, latest_release is the same as release_path if a deploy is in progress, or current_release if not. - Jamis On Sun, Jul 26, 2009 at 8:06 PM, Houdini<[email protected]> wrote: > > release_path: > /home/dima/www/ebank/releases/20090727020410 > > currency_path: > /home/dima/www/ebank/releases/20090727013231 > > Is it ok? > Why it's happend? > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Capistrano" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.co.uk/group/capistrano?hl=en -~----------~----~----~----~------~----~------~--~---
