# Bershelf / git configuration issue?

**URL:** https://discourse.chef.io/t/bershelf-git-configuration-issue/6396
**Category:** Chef Infra (archive)
**Created:** [March 12, 2015, 2:35pm UTC](https://discourse.chef.io/t/bershelf-git-configuration-issue/6396 "2015-03-12T14:35:19Z")
**Posts on this page:** 9
**Page:** 1

<div class="post-metadata">

### Author: ![Chris\_F](https://avatars.discourse-cdn.com/v4/letter/c/fbc32d/32.png) [@Chris\_F](https://discourse.chef.io/u/Chris_F)
#### Post date: [March 12, 2015, 2:35pm UTC](https://discourse.chef.io/t/bershelf-git-configuration-issue/6396/1 "2015-03-12T14:35:19Z")

</div>

I posted this in stackoverflow [http://stackoverflow.com/questions/28996765/how-do-i-setup-cookbooks-in-git-for-berkshelf](http://stackoverflow.com/questions/28996765/how-do-i-setup-cookbooks-in-git-for-berkshelf), but I thought I’d post it here too.  
I’m trying to use Berkshelf, and am trying the following simple test.  
We have an internal git server using Gitlab, say, [http://git-server.domain.com](http://git-server.domain.com). I created a “project” group, and pushed mycookbook.git repo so, according to git, the cookbook is accessible via [http://git-server.domain.com/project/mycookbook.git](http://git-server.domain.com/project/mycookbook.git).  
Now I have an environment cookbook called myapp\_dev, and its Berksfile looks like this  
source "[https://supermarket.chef.io](https://supermarket.chef.io)"  
source “[http://git-server.domain.com/project](http://git-server.domain.com/project)”

metadata  
and its metadata.rb looks like this  
name ‘myapp\_dev’  
(snip)  
version ‘0.1.0’

depends ‘mycookbook’, '~\> 1.0.0’  
When I do a berks install, I get  
Required artifacts do not exist at the desired version  
Missing artifacts: mycookbook  
Unable to find a solution for demands: mycookbook(\>= 0.0.0), myapp\_dev (0.1.0)  
What do I have configured wrong?  
Chris

---

<div class="post-metadata">

### Author: ![jdunn](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/jdunn/32/1800_2.png) [@jdunn](https://discourse.chef.io/u/jdunn)
#### Post date: [March 12, 2015, 2:42pm UTC](https://discourse.chef.io/t/bershelf-git-configuration-issue/6396/2 "2015-03-12T14:42:51Z")

</div>

On Thu, Mar 12, 2015 at 10:35 AM, Fouts, Chris [Chris.Fouts@sensus.com](mailto:Chris.Fouts@sensus.com) wrote:

> I posted this in stackoverflow  
> [chef infra - How do I setup cookbooks in git for berkshelf? - Stack Overflow](http://stackoverflow.com/questions/28996765/how-do-i-setup-cookbooks-in-git-for-berkshelf),  
> but I thought I’d post it here too.

It'd be great if you'd stick to one or the other so that the answer  
shows up in a single place.

> I’m trying to use Berkshelf, and am trying the following simple test.
> 
> We have an internal git server using Gitlab, say,  
> [http://git-server.domain.com](http://git-server.domain.com). I created a "project" group, and pushed  
> mycookbook.git repo so, according to git, the cookbook is accessible via  
> [http://git-server.domain.com/project/mycookbook.git](http://git-server.domain.com/project/mycookbook.git).
> 
> Now I have an environment cookbook called myapp\_dev, and its Berksfile looks  
> like this
> 
> source "[https://supermarket.chef.io](https://supermarket.chef.io)"  
> source "[http://git-server.domain.com/project](http://git-server.domain.com/project)"

I don't think this is going to do what you want because your Git  
server doesn't have a /universe endpoint for Berkshelf to use.

You can specify the source of cookbooks individually on the 'depends'  
lines (the syntax is similar to that in a Gemfile and it's documented  
on [berkshelf.com](http://berkshelf.com)) or you can run your own supermarket internally.

- Julian

--  
[Julian C. Dunn [jdunn@aquezada.com](mailto:jdunn@aquezada.com) \* Sorry, I'm ]  
[WWW: [Julian Dunn's Blog - Commentary on media, technology, and everything in between.](http://www.aquezada.com/staff/julian) \* only Web 1.0 ]  
[gopher://sdf.org/1/users/keymaker/ \* compliant!]  
[PGP: 91B3 7A9D 683C 7C16 715F 442C 6065 D533 FDC2 05B9]

---

<div class="post-metadata">

### Author: ![Chris\_F](https://avatars.discourse-cdn.com/v4/letter/c/fbc32d/32.png) [@Chris\_F](https://discourse.chef.io/u/Chris_F)
#### Post date: [March 12, 2015, 2:56pm UTC](https://discourse.chef.io/t/bershelf-git-configuration-issue/6396/3 "2015-03-12T14:56:14Z")

</div>

Thanks Julian.

I resisted cross-posting here but I got no traction in stackoverflow. I will post your answer there.

You said...  
"  
I don't think this is going to do what you want because your Git server doesn't have a /universe endpoint for Berkshelf to use.

You can specify the source of cookbooks individually on the 'depends'  
lines (the syntax is similar to that in a Gemfile and it's documented on [berkshelf.com](http://berkshelf.com)) or you can run your own supermarket internally.  
"

This makes sense. I will explore specifying the git repo per cookbook in my Berksfile as an initial attempt, and then look into running a supermarket internally.

Thanks,  
Chris

-----Original Message-----  
From: Julian C. Dunn [[mailto:jdunn@aquezada.com](mailto:jdunn@aquezada.com)]  
Sent: Thursday, March 12, 2015 10:43 AM  
To: [chef@lists.opscode.com](mailto:chef@lists.opscode.com)  
Subject: [chef] Re: Bershelf / git configuration issue?

On Thu, Mar 12, 2015 at 10:35 AM, Fouts, Chris [Chris.Fouts@sensus.com](mailto:Chris.Fouts@sensus.com) wrote:

> I posted this in stackoverflow  
> [chef infra - How do I setup cookbooks in git for berkshelf? - Stack Overflow](http://stackoverflow.com/questions/28996765/how-do-i-setup-cookbooks-i)  
> n-git-for-berkshelf,  
> but I thought I’d post it here too.

It'd be great if you'd stick to one or the other so that the answer shows up in a single place.

> I’m trying to use Berkshelf, and am trying the following simple test.
> 
> We have an internal git server using Gitlab, say,  
> [http://git-server.domain.com](http://git-server.domain.com). I created a "project" group, and pushed  
> mycookbook.git repo so, according to git, the cookbook is accessible  
> via [http://git-server.domain.com/project/mycookbook.git](http://git-server.domain.com/project/mycookbook.git).
> 
> Now I have an environment cookbook called myapp\_dev, and its Berksfile  
> looks like this
> 
> source "[https://supermarket.chef.io](https://supermarket.chef.io)"  
> source "[http://git-server.domain.com/project](http://git-server.domain.com/project)"

I don't think this is going to do what you want because your Git server doesn't have a /universe endpoint for Berkshelf to use.

You can specify the source of cookbooks individually on the 'depends'  
lines (the syntax is similar to that in a Gemfile and it's documented on [berkshelf.com](http://berkshelf.com)) or you can run your own supermarket internally.

- Julian

--  
[Julian C. Dunn [jdunn@aquezada.com](mailto:jdunn@aquezada.com) \* Sorry, I'm ]  
[WWW: [Julian Dunn's Blog - Commentary on media, technology, and everything in between.](http://www.aquezada.com/staff/julian) \* only Web 1.0 ]  
[gopher://sdf.org/1/users/keymaker/ \* compliant!]  
[PGP: 91B3 7A9D 683C 7C16 715F 442C 6065 D533 FDC2 05B9]

---

<div class="post-metadata">

### Author: ![Michael\_Glenney](https://avatars.discourse-cdn.com/v4/letter/m/a9adbd/32.png) [@Michael\_Glenney](https://discourse.chef.io/u/Michael_Glenney)
#### Post date: [March 12, 2015, 4:39pm UTC](https://discourse.chef.io/t/bershelf-git-configuration-issue/6396/4 "2015-03-12T16:39:14Z")

</div>

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](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](https://git-server.domain.com/mycookbook.git)',  
ref: 'eef7e65806e7ff3bdbe148e27c447ef4a8bc3881'

There's a couple other ways you can find at [http://berkshelf.com](http://berkshelf.com)

berkshelf-api might be an option ([GitHub - berkshelf/berkshelf-api: Berkshelf dependency API server](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 (  
[GitHub - chef/supermarket: Chef's community platform](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 [Chris.Fouts@sensus.com](mailto:Chris.Fouts@sensus.com)  
wrote:

> Thanks Julian.
> 
> I resisted cross-posting here but I got no traction in stackoverflow. I  
> will post your answer there.
> 
> You said...  
> "  
> I don't think this is going to do what you want because your Git server  
> doesn't have a /universe endpoint for Berkshelf to use.
> 
> You can specify the source of cookbooks individually on the 'depends'  
> lines (the syntax is similar to that in a Gemfile and it's documented on  
> [berkshelf.com](http://berkshelf.com)) or you can run your own supermarket internally.  
> "
> 
> This makes sense. I will explore specifying the git repo per cookbook in  
> my Berksfile as an initial attempt, and then look into running a  
> supermarket internally.
> 
> Thanks,  
> Chris
> 
> -----Original Message-----  
> From: Julian C. Dunn [[mailto:jdunn@aquezada.com](mailto:jdunn@aquezada.com)]  
> Sent: Thursday, March 12, 2015 10:43 AM  
> To: [chef@lists.opscode.com](mailto:chef@lists.opscode.com)  
> Subject: [chef] Re: Bershelf / git configuration issue?
> 
> On Thu, Mar 12, 2015 at 10:35 AM, Fouts, Chris [Chris.Fouts@sensus.com](mailto:Chris.Fouts@sensus.com)  
> wrote:
> 
> > I posted this in stackoverflow  
> > [chef infra - How do I setup cookbooks in git for berkshelf? - Stack Overflow](http://stackoverflow.com/questions/28996765/how-do-i-setup-cookbooks-i)  
> > n-git-for-berkshelf,  
> > but I thought I’d post it here too.
> 
> It'd be great if you'd stick to one or the other so that the answer shows  
> up in a single place.
> 
> > I’m trying to use Berkshelf, and am trying the following simple test.
> > 
> > We have an internal git server using Gitlab, say,  
> > [http://git-server.domain.com](http://git-server.domain.com). I created a "project" group, and pushed  
> > mycookbook.git repo so, according to git, the cookbook is accessible  
> > via [http://git-server.domain.com/project/mycookbook.git](http://git-server.domain.com/project/mycookbook.git).
> > 
> > Now I have an environment cookbook called myapp\_dev, and its Berksfile  
> > looks like this
> > 
> > source "[https://supermarket.chef.io](https://supermarket.chef.io)"  
> > source "[http://git-server.domain.com/project](http://git-server.domain.com/project)"
> 
> I don't think this is going to do what you want because your Git server  
> doesn't have a /universe endpoint for Berkshelf to use.
> 
> You can specify the source of cookbooks individually on the 'depends'  
> lines (the syntax is similar to that in a Gemfile and it's documented on  
> [berkshelf.com](http://berkshelf.com)) or you can run your own supermarket internally.
> 
> - Julian
> 
> --  
> [Julian C. Dunn [jdunn@aquezada.com](mailto:jdunn@aquezada.com) \* Sorry, I'm ]  
> [WWW: [Julian Dunn's Blog - Commentary on media, technology, and everything in between.](http://www.aquezada.com/staff/julian) \* only Web 1.0 ]  
> [gopher://sdf.org/1/users/keymaker/ \* compliant!]  
> [PGP: 91B3 7A9D 683C 7C16 715F 442C 6065 D533 FDC2 05B9]

---

<div class="post-metadata">

### Author: ![Chris\_F](https://avatars.discourse-cdn.com/v4/letter/c/fbc32d/32.png) [@Chris\_F](https://discourse.chef.io/u/Chris_F)
#### Post date: [March 12, 2015, 5:24pm UTC](https://discourse.chef.io/t/bershelf-git-configuration-issue/6396/5 "2015-03-12T17:24:54Z")

</div>

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:mike.glenney@gmail.com](mailto:mike.glenney@gmail.com)]  
Sent: Thursday, March 12, 2015 12:39 PM  
To: [chef@lists.opscode.com](mailto:chef@lists.opscode.com)  
Subject: [chef] Re: RE: Re: Bershelf / git configuration issue?

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](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](https://git-server.domain.com/mycookbook.git)', ref: 'eef7e65806e7ff3bdbe148e27c447ef4a8bc3881'

There's a couple other ways you can find at [http://berkshelf.com](http://berkshelf.com)

berkshelf-api might be an option ([GitHub - berkshelf/berkshelf-api: Berkshelf dependency API server](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 ([GitHub - chef/supermarket: Chef's community platform](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 \<[Chris.Fouts@sensus.com](mailto:Chris.Fouts@sensus.com)[mailto:Chris.Fouts@sensus.com](mailto:Chris.Fouts@sensus.com)\> wrote:  
Thanks Julian.

I resisted cross-posting here but I got no traction in stackoverflow. I will post your answer there.

You said...  
"  
I don't think this is going to do what you want because your Git server doesn't have a /universe endpoint for Berkshelf to use.

You can specify the source of cookbooks individually on the 'depends'  
lines (the syntax is similar to that in a Gemfile and it's documented on [berkshelf.com](http://berkshelf.com)[http://berkshelf.com](http://berkshelf.com)) or you can run your own supermarket internally.  
"

This makes sense. I will explore specifying the git repo per cookbook in my Berksfile as an initial attempt, and then look into running a supermarket internally.

Thanks,  
Chris

-----Original Message-----  
From: Julian C. Dunn [[mailto:jdunn@aquezada.com](mailto:jdunn@aquezada.com)[mailto:jdunn@aquezada.com](mailto:jdunn@aquezada.com)]  
Sent: Thursday, March 12, 2015 10:43 AM  
To: [chef@lists.opscode.com](mailto:chef@lists.opscode.com)[mailto:chef@lists.opscode.com](mailto:chef@lists.opscode.com)  
Subject: [chef] Re: Bershelf / git configuration issue?

On Thu, Mar 12, 2015 at 10:35 AM, Fouts, Chris \<[Chris.Fouts@sensus.com](mailto:Chris.Fouts@sensus.com)[mailto:Chris.Fouts@sensus.com](mailto:Chris.Fouts@sensus.com)\> wrote:

> I posted this in stackoverflow  
> [chef infra - How do I setup cookbooks in git for berkshelf? - Stack Overflow](http://stackoverflow.com/questions/28996765/how-do-i-setup-cookbooks-i)  
> n-git-for-berkshelf,  
> but I thought I’d post it here too.

It'd be great if you'd stick to one or the other so that the answer shows up in a single place.

> I’m trying to use Berkshelf, and am trying the following simple test.
> 
> We have an internal git server using Gitlab, say,  
> [http://git-server.domain.com](http://git-server.domain.com). I created a "project" group, and pushed  
> mycookbook.git repo so, according to git, the cookbook is accessible  
> via [http://git-server.domain.com/project/mycookbook.git](http://git-server.domain.com/project/mycookbook.git).
> 
> Now I have an environment cookbook called myapp\_dev, and its Berksfile  
> looks like this
> 
> source "[https://supermarket.chef.io](https://supermarket.chef.io)"  
> source "[http://git-server.domain.com/project](http://git-server.domain.com/project)"

I don't think this is going to do what you want because your Git server doesn't have a /universe endpoint for Berkshelf to use.

You can specify the source of cookbooks individually on the 'depends'  
lines (the syntax is similar to that in a Gemfile and it's documented on [berkshelf.com](http://berkshelf.com)[http://berkshelf.com](http://berkshelf.com)) or you can run your own supermarket internally.

- Julian

--  
[Julian C. Dunn \<[jdunn@aquezada.com](mailto:jdunn@aquezada.com)[mailto:jdunn@aquezada.com](mailto:jdunn@aquezada.com)\> \* Sorry, I'm ]  
[WWW: [Julian Dunn's Blog - Commentary on media, technology, and everything in between.](http://www.aquezada.com/staff/julian) \* only Web 1.0 ]  
[gopher://sdf.org/1/users/keymaker/[http://sdf.org/1/users/keymaker/](http://sdf.org/1/users/keymaker/) \* compliant! ]  
[PGP: 91B3 7A9D 683C 7C16 715F 442C 6065 D533 FDC2 05B9]

---

<div class="post-metadata">

### Author: ![jdunn](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/jdunn/32/1800_2.png) [@jdunn](https://discourse.chef.io/u/jdunn)
#### Post date: [March 13, 2015, 8:22pm UTC](https://discourse.chef.io/t/bershelf-git-configuration-issue/6396/6 "2015-03-13T20:22:36Z")

</div>

On Thu, Mar 12, 2015 at 12:39 PM, Michael Glenney  
[mike.glenney@gmail.com](mailto:mike.glenney@gmail.com) wrote:

> Though the README ([GitHub - chef/supermarket: Chef's community platform](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).

We're contemplating a solution like making oc-id be able to use  
different auth backends (so kind of like an Atlassian Crowd) -- would  
this be useful?

Another thought I had was what if we just made plugins for artifact  
servers like Nexus or Artifactory to be able to "speak" the  
supermarket protocol, and that way you'd get all the rights management  
out-of-the-box. Is that of interest to folks?

- Julian

---

<div class="post-metadata">

### Author: ![tknerr](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/tknerr/32/21_2.png) [@tknerr](https://discourse.chef.io/u/tknerr)
#### Post date: [March 13, 2015, 9:40pm UTC](https://discourse.chef.io/t/bershelf-git-configuration-issue/6396/7 "2015-03-13T21:40:29Z")

</div>

+1 for making nexus, artifactory, bintray etc speak the supermarket protocol.

They seem to be quite common and widespread artifact repositories (at  
least among the customers I worked with).

Would love to see them speaking chef.

Cheers, Torben

On Fri, Mar 13, 2015 at 9:22 PM, Julian C. Dunn [jdunn@aquezada.com](mailto:jdunn@aquezada.com) wrote:

> On Thu, Mar 12, 2015 at 12:39 PM, Michael Glenney  
> [mike.glenney@gmail.com](mailto:mike.glenney@gmail.com) wrote:
> 
> > Though the README ([GitHub - chef/supermarket: Chef's community platform](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).
> 
> We're contemplating a solution like making oc-id be able to use  
> different auth backends (so kind of like an Atlassian Crowd) -- would  
> this be useful?
> 
> Another thought I had was what if we just made plugins for artifact  
> servers like Nexus or Artifactory to be able to "speak" the  
> supermarket protocol, and that way you'd get all the rights management  
> out-of-the-box. Is that of interest to folks?
> 
> - Julian

---

<div class="post-metadata">

### Author: ![Aimelyne\_Mochiron](https://avatars.discourse-cdn.com/v4/letter/a/73ab20/32.png) [@Aimelyne\_Mochiron](https://discourse.chef.io/u/Aimelyne_Mochiron)
#### Post date: [March 14, 2015, 10:04am UTC](https://discourse.chef.io/t/bershelf-git-configuration-issue/6396/8 "2015-03-14T10:04:15Z")

</div>

+1 - that would be very, very convenient.

Cheers,

am

On 13 Mar 2015, at 23:40, Torben Knerr [mail@tknerr.de](mailto:mail@tknerr.de) wrote:

> +1 for making nexus, artifactory, bintray etc speak the supermarket protocol.
> 
> They seem to be quite common and widespread artifact repositories (at  
> least among the customers I worked with).
> 
> Would love to see them speaking chef.
> 
> Cheers, Torben
> 
> On Fri, Mar 13, 2015 at 9:22 PM, Julian C. Dunn [jdunn@aquezada.com](mailto:jdunn@aquezada.com) wrote:
> 
> > On Thu, Mar 12, 2015 at 12:39 PM, Michael Glenney  
> > [mike.glenney@gmail.com](mailto:mike.glenney@gmail.com) wrote:
> > 
> > > Though the README ([GitHub - chef/supermarket: Chef's community platform](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).
> > 
> > We're contemplating a solution like making oc-id be able to use  
> > different auth backends (so kind of like an Atlassian Crowd) -- would  
> > this be useful?
> > 
> > Another thought I had was what if we just made plugins for artifact  
> > servers like Nexus or Artifactory to be able to "speak" the  
> > supermarket protocol, and that way you'd get all the rights management  
> > out-of-the-box. Is that of interest to folks?
> > 
> > - Julian

---

<div class="post-metadata">

### Author: ![Nico\_Kadel\_Garcia](https://avatars.discourse-cdn.com/v4/letter/n/ad7895/32.png) [@Nico\_Kadel\_Garcia](https://discourse.chef.io/u/Nico_Kadel_Garcia)
#### Post date: [March 18, 2015, 6:36pm UTC](https://discourse.chef.io/t/bershelf-git-configuration-issue/6396/9 "2015-03-18T18:36:39Z")

</div>

> -----Original Message-----  
> From: Julian C. Dunn [[mailto:jdunn@aquezada.com](mailto:jdunn@aquezada.com)]  
> Sent: Friday, March 13, 2015 4:23 PM  
> To: [chef@lists.opscode.com](mailto:chef@lists.opscode.com)  
> Subject: [chef] Re: Re: RE: Re: Bershelf / git configuration issue?
> 
> On Thu, Mar 12, 2015 at 12:39 PM, Michael Glenney  
> [mike.glenney@gmail.com](mailto:mike.glenney@gmail.com) wrote:
> 
> > Though the README ([GitHub - chef/supermarket: Chef's community platform](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).
> 
> We're contemplating a solution like making oc-id be able to use different auth  
> backends (so kind of like an Atlassian Crowd) -- would this be useful?
> 
> Another thought I had was what if we just made plugins for artifact servers like  
> Nexus or Artifactory to be able to "speak" the supermarket protocol, and that  
> way you'd get all the rights management out-of-the-box. Is that of interest to  
> folks?

I personally gave up on the chef server requirement for small environments some time ago, and use Berkshelf with chef-solo. It doesn't allow environment auditing, but most tools allow manual listing of cluster members and other configurations. It's also invaluable for configuring, or bootstrapping, the initial chef server to support the other environments.

Nico Kadel-Garcia  
Lead DevOps Engineer  
[nkadel@skyhookwireless.com](mailto:nkadel@skyhookwireless.com)
