Rails - Apr 2008 - Webistrano recipes association (was: [Capistrano] Webistrano 1.3 released)

I see at some point recipes were changed from project-associated to
stage-associated, is there some explanation or examples of that use-case?

Could I request we have both? In my current cap scripts, we don''t have
any
stage-specific recipes, but maybe I''m just not understanding this
completely.

On Tue, Apr 29, 2008 at 1:04 PM, Jonathan Weiss
<jw-eM0Q5iXcOashFhg+JK9F0w@public.gmane.org> wrote:
>
> Cheers,
>
> I''m proud to announce Webistrano 1.3.
>
> http://labs.peritor.com/webistrano/
>
> Webistrano is a Web UI for managing Capistrano deployments. It lets you
> manage projects and their stages like test, production, and staging with
> different settings. Those stages can then be deployed with Capistrano
> through Webistrano.
>
> The 1.3 adds several new shiny features to Webistrano that make
> deployment easier:
>
>     * Better Git support through Capistrano 2.2
>     * Support for Phusion Passenger / mod_rails
>     * Ability to temporary disable hosts for a deployment
>     * A command-line interface with script/deploy
>     * A simple permission system
>
> The complete changelog is available through the Webistrano project site.
> http://labs.peritor.com/webistrano/browser/branches/1.3/CHANGELOG.txt
>
> One very often demanded feature is the ability to temporary disable a
> host for a deployment. This is helpful when you want to deploy a stage
> without changing the stage configuration even if one or more hosts are
> down. Another scenario is when you want to execute a task only on a
> limited set of servers.
>
> The script/deploy command is a nice little gem, especially useful if you
> want to script Webistrano:
>
> $ ruby script/deploy
> Usage: deploy [options] project stage
>     -h, --help                       This message
>     -e, --environment=ENV            RAILS_ENV for Webistrano (default:
> production)
>     -u, --username=NAME              Webistrano username to use
> (default: admin)
>     -t, --task=NAME                  Capistrano task to invoke
> (default: deploy)
>     -d, --description=TEXT           Deployment comment for Webistrano
> records
>
> Further, Webistrano now offers built-in tasks for managing mod_rails
> deployments. It will override the default deploy tasks and ask for the
> necessary configuration entries so that using mod_rails becomes even
> easier.
>
> Webistrano 1.3 can be downloaded here.
>
> http://labs.peritor.com/webistrano/wiki/Download
>
> Webistrano is BSD-licensed and the project site is open for everybody.
> Please see the project page for more documentation and screenshots.
> There are even some screencasts.
>
> http://labs.peritor.com/webistrano/
>
> Jonathan
>
> --
> Jonathan Weiss
> http://blog.innerewut.de
> http://twitter.com/jweiss
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Hi Dean,

Dean Holdren wrote:
> I see at some point recipes were changed from project-associated to 
> stage-associated, is there some explanation or examples of that use-case?
>  
Recipes were moved from the project level to the stage level with 
Webistrano 1.1 so that different stages of a project can have different 
recipes. This was a feature commonly requested and makes sense if your 
recipes set up resources like symlinks to upload dirs that should be 
different for each stage.

In order to replicate the old behavior just add the recipes to each stage.
> Could I request we have both? 
Why not, it would then also mimic the configuration parameters that can 
be set at the project and the stage level. If you have any patches for 
this kind of changes, please post them at the trac/wiki.

Jonathan

-- 
Jonathan Weiss
http://blog.innerewut.de
http://twitter.com/jweiss

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---