Greg,

I've got some ideas for adding that to cap2, though for now I'm  
focusing on stabilizing what I've got.

- Jamis

On Apr 5, 2007, at 5:22 AM, Greg Hauptmann wrote:

> Jamis,
>
> What do you think about integrating the technique from Mike Clark's  
> blog at the bottom section ("The Cadillac Approach") of http:// 
> clarkware.com/cgi/blosxom/2007/01/18#ManagingVersionsWithCap ?
>
> This would be a good value add / "lighter weight" deployment option  
> for those who need to manage rails in the vendor area (e.g. for  
> those on managed/shared hosting providers).
>
> I did note the common.rake file referenced seems to have a bug that  
> I'm looking at now.  It seems to just check out  Rails Edge as  
> opposed to checking out the particular revision you configure.  I'm  
> intended to modify it for myself so you configure the rails TAG  
> version you want as I'm only going to be sticking to stable versions.
>
> Regards
> Greg
>
> On 3/6/07, Lori Olson <[EMAIL PROTECTED]> wrote: Mike Clark had  
> some interesting stuff to say about piston, and about an  
> alternative approach that he uses.
>
> http://clarkware.com/cgi/blosxom/2007/01/18#ManagingVersionsWithCap
> http://clarkware.com/cgi/blosxom/2007/01/22#ManagingPluginsWithPiston
>
> On 2/26/07, Clayton Cottingham <[EMAIL PROTECTED]> wrote:
> Was wondering if there was any concensus on how to best use  
> svn:externals, if at all!
>
>
> I scanned the group and it seems like having them in a deploy  
> recipe can cause connection errors
>
>
> Thery suggested piston
>
> http://piston.rubyforge.org/
>
>
> I don't want to run into deployment issues where the svn:externals  
> break my code but I would like to use some plugins etc
>
>
> So piston sounds like the right thing to do
>
>
>  Any other thoughts?
>
>
>
>
>
>
>
>
>
>
>
>
>
> >


--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/capistrano
-~----------~----~----~----~------~----~------~--~---

Reply via email to