Hi,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.
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.
Archive powered by MHonArc 2.6.16.