Hi Lee,
> I look forward to any more feedback, positive or negative or otherwise:
I agree with everybody else that the 2.5 line shouldn't have any
incompabitle changes.
>.. 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
This is not my experience, I see most people just overrding the
deploy:{start|stop|restart} tasks with NOPs.
I think that an app-stack aware extension to Capistrano is really
useful, but I'm not sure this is the right way. I've been very busy
the last weeks with conferences and will look over the changes over
the coming days. Maybe we should start a discussion on the desired API
first (what and how people want to use app-stack aware extensions) and
then start the implementation.
Because we are breaking/changing the default behavior this would also
be more stuff for a 3.0 release.
Jonathan
--
Jonathan Weiss
http://blog.innerewut.de
http://twitter.com/jweiss
--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at http://groups.google.com/group/capistrano
-~----------~----~----~----~------~----~------~--~---
