[chef] Re: Re: Re: Re: Large cookbook uploads fail with "unauthorized" after data upload

["Jason J. W. Williams" < >]

On Mon, Mar 26, 2012 at 2:35 PM, Sascha Bates 
<
 >
 wrote:
> When I last worked on something like this, we found it much easier to
> maintain a file repository external to Chef.  This kept both Chef and
> Subversion from puking on us, since both tend to dislike large binaries.

Everything that's deployed into production that has been modified by
us (like these packages) is checked into a Git repo, period. That
ensures we can rollback and have a change history of who put what in.
Git has handled this quite adroitly for us.


> It's also kinder to store large files outside your chef/source control in
> regards to users who are updating against those repositories.  The last
> thing I want is to end up downloading large binaries into my working copy.

A nice sentiment, but our engineers who are working on the affected
recipes need the custom packages that they depend on anyway.

> Just some thoughts from someone who's been there.

Appreciated, but our experience has been quite different through trial
and error over the past 7 years with our services.

-J