Hi Lee, I've just tried a fresh new deploy. It went smooth. On Wed, May 27, 2009 at 1:27 AM, Lee Hambley <[email protected]> wrote:
> .. why has all this stuff gone? Well the migrations, and shared children, > everyone deploying Rails needs, but anyone using Sinatra, PHP, python or > similar.. ends up having to skip loading `deploy.rb` and not even getting > the versioned deploy code. Now, out of the box, a deploy will make a new > release directory, use your deploy:strategy to get the code into it and then > update the symlink. There is more in the > CHANGELOG.rdoc<http://github.com/capistrano/capistrano/blob/bee80924105203cfd8840d434a0f1fdd7e64e7b2/CHANGELOG.rdoc> > Although I agree with you, I think a maintenance release (as this one is expected to be because belongs to 2.5.x) should not come with deep changes in the way it works. If you decide to go ahead with those changes, may I suggest a different release number? IMHO, at least a mini release (2.6.) would be more appropriate. I'm always reluctant to make a change that breaks existing functionality > without notifying the user of a workaround, usually with a deprecation > notice. +1 When an existing user tries and fails to run deploy:migrate, what will they > see and how will they know what to do? > This is the message. mac-carletti:trunk carletti$ cap deploy:migrate > the task `deploy:migrate' does not exist > I think this is not a friendly direction. Many users don't know much more about capistrano than - install the gem - adapt those lines -- Simone Carletti Site & Blog: http://www.simonecarletti.com Email: [email protected] LinkedIn: http://linkedin.com/in/weppos Nick: weppos | Skype: weppos --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
