Jesse Nelson
Jesse Nelson
This is sorta related to the uniformity discussion of GET/POST/PUT in #22 Today i wrote a lil cookbook downloader, and the inflexability of chef.Get was brought to light. even with...
would be nice to pull the chef-crypto out into its own library. Was discussing this a bit with @ctdk merging client and server crypto into a separate lib. open for...
Right now this is hardcoded. Should be an option in `Connect` method. Maybe even build out a config lib and move this out of api?
Would be sweet to have a Makefile or a go-get able setup that doesn't require heroku buildpack to build. Mainly it's just getting the right deps in place and running...
idea to get rid of the magicRequest \* is to maybe build up an interface thats a chef-request ? not sure if thats the best way to do it or...
Most of the services are implemented as a veneer over the Server API. Some services have higher level methods. I think we should maybe move these into a specific porcelain...
Would be good to break out the client bits of http.go then each service into their own packages. The model with the service struct embedding a client should serve this...
In the "Hints" section theres a recommendation to use global variables. This seems like leading someone down a path of bad habits. In the provided use case the global seems...
Operations only work on repos that have 'loose' refs to tags i.e. have not been GC'd. Probably also goes for packed heads/remotes