[chef] Re: Re: Best way to install from tarballs??

[Ranjib Dey < >]

Indeed , even we do use the same strategy to deploy some of  our apps. We have the fpm mediated rpm creation step as part of our CI. Also, there are mcollective based triggers that executed "createrepo" on the rpm repo server and "chef-client --once " to the app servers. But as things evolved,     in some cases we are overburdened with git-fpm--publish-createrepo-chef route and in some other cases we have many sources of truth (rpm version/ git commit hash). As of now , i dont see a 'one solution fits all situation' approach for distributing build artifacts. But never the less we should work/innovate towards that

On Fri, Jan 20, 2012 at 9:24 PM, Zac Stevens < " target="_blank"> > wrote:

On Fri, Jan 20, 2012 at 2:28 PM, Van Fossan,Randy < " target="_blank"> > wrote:

> How is the best way to handle installations from tarballs?  Currently, we
> have several tarballs that we use to deploy software.  These tarballs are
> just extracted to the correct directory and the software is installed.

We started out with a "tar_package" LWRP, similar to the approach
mentioned by the other replies on this thread, but now use FPM[1] to
create RPMs of the file we previously shipped in a tarball.  The
tarballs we're concerned with are updated very infrequently, so the
extra step of building the RPM isn't a problem for us.


Zac

[1]: https://github.com/jordansissel/fpm