4 ms·
Coming from npm, composer, bundler, and utilities like those I wasn't entirely happy with Godep. Instead there's Glide[1]. Sure, Godep lets you save and restor
by mfer 12y ago
Coming from npm, composer, bundler, and utilities like those I wasn't entirely happy with Godep. Instead there's Glide[1].
Sure, Godep lets you save and restore dependencies to your GOPATH. But, what if different projects with different versions of dependencies? Or, what if you want to track to branches?
There's a reason npm, bundler, and composer are popular. They are useful. That's why I've become a happy glide user (and contributor).
Just my 2 cents.
[1] https://github.com/Masterminds/glide https://github.com/Masterminds/glide
- kolev 12y agoThanks! I didn't know Glide, but I'm in love at first sight!
- sudhirj 12y agoAny word on how you'd use glide during deployment? Say on a build machine, or when deploying to Heroku?
- mfer 12y agoIf you're looking for a Heroku buildpack to install your dependencies and build your binary I'm not aware of one. But, that would be a useful idea. Even something that could be used for Cloud Foundry as well. On a build machine you'd do a `glide install` to get the dependencies installed, set the gopath (there are a couple ways to do it), and then go build per usual. From there you can deploy the binary as needed.
- nulltype 12y agoGlide sounds pretty cool, but how is it better than just setting your GOPATH on a per-project basis?
- coldtea 12y agoIn that you don't have to set your GOPATH on a per-project basis?
- mfer 12y agoGlide attempts to automate some of that. For example, Glide knows what your GOPATH for a project should be and using `glide in` your GOPATH is set. No needing to remember it. Using `glide install` will read the dependencies listed in the yaml file and install them while setting them to the specified version in the same place your GOPATH should be for the project. It simplified GOPATH handling in addition to working with dependencies.