You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 12, 2018. It is now read-only.
We'd love to start contributing to your mongodb recipe and use it in our platform (with berkshelf support). For this we need it to be its own repository. Will you consider separating them?
Thanks!
The text was updated successfully, but these errors were encountered:
Yes, that is in the plan. We have not yet started to execute on this plan. I hesitate to make any statements about when it might be scheduled but maybe check back this summer? I understand how much easier it makes working with cookbooks to have them separated.
In the mean time, berkshelf can actually work with a github repo that contains a cookbooks directory. The example on berkshelf.com reads: 'An optional rel key can be specified if your repository contains many cookbooks in a single repository under a sub-directory or at root. eg cookbook "rightscale", git: "https://github.com/rightscale/rightscale_cookbooks.git", rel: "cookbooks/rightscale"'
I haven't done this yet; I'm curious if it works for you.
Thank you for reporting this issue and appreciate your patience. We've notified the core team for an update on this issue. We're looking for a response within the next 30 days or the issue may be closed.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We'd love to start contributing to your mongodb recipe and use it in our platform (with berkshelf support). For this we need it to be its own repository. Will you consider separating them?
Thanks!
The text was updated successfully, but these errors were encountered: