Yep that’s what I ended up doing, i.e., adding the git repo on the cookbook line. I appreciate all the responses, and they gave me more avenues to explore. Chris From: Michael Glenney [mailto:
You can't set your git server as a source in Berksfile as Julian said but you can target cookbooks in your git repo: cookbook 'mycookbook', git: 'https://git-server.domain.com/mycookbook.git', tag: 'v1.0.0' or maybe with a commit hash cookbook 'mycookbook', git: 'https://git-server.domain.com/mycookbook.git', ref: 'eef7e65806e7ff3bdbe148e27c447ef4a8bc3881' There's a couple other ways you can find at
http://berkshelf.com berkshelf-api might be an option (https://github.com/berkshelf/berkshelf-api) if you're running github enterprise. I thought it was going away but I see recent commits. Some time
ago I wanted to point it at Gitlab but it wasn't supported. README says it only support github enterprise (and then proceeds to discourage actually doing it). You can run your own supermarket but I'm pretty sure you have to also run chef server or you can't
authenticate against it. Though the README (https://github.com/chef/supermarket) indicates there may be a hack coming down the pipe soon: "NOTE: Authentication currently requires a live chef server running oc-id. We are working on a solution which would allow a developer to run the authentication locally, stay tuned" I personally hope so because I think it's pretty lame they make you run a chef server (If I remember right berkshelf was originally created for workflows and orgs that were NOT running a chef server which makes it even more frustrating). Sorry I hijacked your thread to rant about this particular issue about an otherwise awesome platform (Chef <3). It's just always really bothered me how that shook out and your question brought it all back to the surface. Hopefully you
got some value from technical part of my response :) MG On Thu, Mar 12, 2015 at 7:56 AM, Fouts, Chris <
" target="_blank">
> wrote: Thanks Julian.
|
Archive powered by MHonArc 2.6.16.