Cool, I like a lot of those recap ideas.  The releases/* directories do seem a 
bit redundant with git now.


On 7/02/2014, at 23:53 , Jeremy Olliver <[email protected]> wrote:

> I believe most chef or puppet deployment usage is in a continuous deployment 
> manner (deploying latest passing builds from a CI server).
> 
> We're still using chef to setup a server, but Capistrano v2 (with our own 
> extension gem easy-deployment) to deploy.
> 
> Something else worth looking at is recap, which is Capistrano (2?) under the 
> hood, but rewrites tasks for speed - no releases dir, directly runs the app 
> from the git clone, and only bundle or asset if the relevant files have 
> changed. Obviously it comes with some fairly heavy choices/conventions to 
> support this. Codeclimate have a blog post on the topic I think.
> 
> Cheers,
> Jeremy
> 
> On Friday, February 7, 2014, Nahum Wild <[email protected]> wrote:
> I've heard of Chef and/or Puppet being used.
> 
> Anyone know what do the continuous integration tools use?
> 
> 
> --nahum
> 
> 
> On Fri, Feb 7, 2014 at 10:59 PM, Will Bryant <[email protected]> wrote:
> What are people using for deploying their apps these days?
> 
> The current maintainer of Capistrano has based v3 on a GPLed library (SSHkit) 
> and his lawyers and ours have a difference of opinion as to whether this 
> makes Capistrano GPL too 
> (https://github.com/capistrano/capistrano/issues/926).  I find the advice he 
> has received from his company's lawyers surprising as to me it implies the 
> see the GPL as the same as the LGPL, which it certainly is not.  Would be 
> interested to hear if anyone else has had their lawyers look at this...
> 
> So anyway, we wouldn't want to take that risk, so what other options are 
> there we should be considering these days?
> 
> Vlad the Deployer had some good stuff when it came out but looking at the 
> current readme and recent commits I get the impression it has fallen out of 
> date a bit.
> 
> There is Mina which I just heard of today, but I haven't tried it.
> 
> Any others we should be looking at?
> 
> --
> You received this message because you are subscribed to the Google Groups 
> "WellRailed" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at http://groups.google.com/group/wellrailed.
> For more options, visit https://groups.google.com/groups/opt_out.
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "WellRailed" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at http://groups.google.com/group/wellrailed.
> For more options, visit https://groups.google.com/groups/opt_out.
> 
> 
> -- 
> Jeremy Olliver
> 
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "WellRailed" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at http://groups.google.com/group/wellrailed.
> For more options, visit https://groups.google.com/groups/opt_out.

-- 
You received this message because you are subscribed to the Google Groups 
"WellRailed" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/wellrailed.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to