-
Notifications
You must be signed in to change notification settings - Fork 17
Consider adding a gem for releasing cookbooks #8
Comments
I haven't even looked at that side of things before. If you want to do a PR I'd be happy to look over it and merge. |
I don't think this would be part of meez TDD as it doesn't relate to testing. Wouldn't a user simply use one of those gems with their cookbook if they wanted to do so? I guess as an extra rake task it might be a good workflow but then it just points back to my statement above :) |
Yep, you could just add one of those gems if you wanted to. I guess why I asked the question is do we want Meez to be purely a way of setting up a cookbook ready for TDD OR as a more general cookbook setup using current/recommended best practices. This isn't something I feel particularly strong about as it is easy enough to add the extra gem manually I just figured that Meez gives you everything needed except an easy way to release your hard work. |
Well knife is how to setup a skel cookbook without TDD, meez would do it for TDD. I also tested meez on an existing cookbook and it works fine. |
heh, meez works on an existing cookbook? I hadn't even looked at targeting that use case yet. |
Yeah, it seemed to work good; even had some intelligence asking me if I wanted to overwrite existing files that existed. I just reviewed files that changed, added things back in if I wanted to before commit and push. It was done on this https://github.com/xhost-cookbooks/system. |
How would everyone feel about adding a recommend (opinionated) way for releasing cookbooks to the community site by adding an extra gem dependancy?
I was thinking either:
The text was updated successfully, but these errors were encountered: