[chef] Re: The future of the deploy resource?


Chronological Thread 
  • From: Lamont Granquist < >
  • To:
  • Subject: [chef] Re: The future of the deploy resource?
  • Date: Fri, 09 Jan 2015 06:55:55 -0800

On 1/9/15 3:20 AM, Roland Moriz wrote:
Hi,

the deploy resource and its provider [1] are very opinionated and tied to 
deployments of Ruby on Rails applications and modeled after the original 
Capistrano workflow defaults. But if you’re not deploying a Rails app, you’re 
pretty much out of luck.
Because of its name and relevance („core resource“), many new chef users fall 
into this trap.

Is it mostly the capistrano default values that are the problem? We could introduce a Chef::Config setting to turn those off, and then eventually make that the default.



Archive powered by MHonArc 2.6.16.

§