On Tue, Jan 23, 2007 at 03:16:22PM -0700, Jamis Buck wrote:
>
> On Jan 23, 2007, at 3:11 PM, Jacob Atzen wrote:
>
> >
> > On Tue, Jan 23, 2007 at 01:54:36PM -0700, Jamis Buck wrote:
> >>> Might I suggest a combination of cached_repository and copy_*?
> >>> Perhaps
> >>> implemented over rsync?
> >>>
> >>> Something along the lines of:
> >>> - Checkout / export into local copy - to avoid having remote repos
> >>> access
> >>> - Rsync local copy to cached repository (or cached export) - to
> >>> minimize
> >>> bandwidth usage and deployment time
> >>> - Copy cached repository to new release
> >>>
> >>> Does this sound like a good idea to anyone but me?
> >>
> >> If you're copying from the localhost to each server anyway, why not
> >> just copy directly to the new release directory? Perhaps I'm
> >> misunderstanding the scenario. At any rate, I think you'll find new
> >> deployment strategies ridiculously easy to write with the new system.
> >> The cached_repository strategy, for instance, is only 48 lines of
> >> code, including blank lines and comments.
> >
> > I'm impatient, when I hit deploy I want my new version running
> > asap. As
> > such I would prefer having a cached copy on each server which I can
> > push
> > deltas to instead of having to push the whole app including the frozen
> > Rails sources.
>
> I think you just described the cached_repository strategy. :) It does
> a complete checkout of the source code once on each server, in the
> shared directory. Then, subsequent deploys just do an update on each
> server's cached copy ("svn up", or whatever the SCM of choice
> supports), and then copy the cached copy to the release directory.
Yeah, I'm suggesting to couple the cached_repository strategy with a
repository only available from the development machine. So far I've been
using the cached_repository trick from blog.caboo.se. It's just that I'd
prefer to push the updates to the servers rather than having the server
pull the updates from the repository as the repository is not easily
accesible from the servers.
I hope my explanations are starting to make sense ;-)
--
Cheers,
- Jacob Atzen
--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/capistrano
-~----------~----~----~----~------~----~------~--~---
