So builds take about 30s on my shitty machine which is pretty long. Turns out golang caches things in $GOPATH/pkg/ but is not clever enough to erase things from there that are out of date. As a result, it was rebuilding everything (including the unchanged dependencies) every build! By completely wiping out $GOPATH/pkg/ and then running `go build -i`, this now takes builds down to about 8 seconds. (After one full build is finished.) This is basically the same as running `go install`, but without copying junk to $GOPATH/bin. Hopefully the tooling will be smart enough to know when to throw out stuff in $GOPATH/pkg automatically and avoid this problem entirely. Is it wrong to send Google a bill for all the extra cpu cycles I've used? ;)
mgmt: next generation config management!
Community:
Come join us in the mgmt community!
| Medium | Link | |
|---|---|---|
| IRC | #mgmtconfig on Freenode | |
| @mgmtconfig & #mgmtconfig | ||
| Mailing list | mgmtconfig-list@redhat.com |
Status:
Mgmt is a fairly new project. We're working towards being minimally useful for production environments. We aren't feature complete for what we'd consider a 1.x release yet. With your help you'll be able to influence our design and get us there sooner!
Documentation:
Please read, enjoy and help improve our documentation!
| Documentation | Additional Notes |
|---|---|
| general documentation | for everyone |
| quick start guide | for mgmt developers |
| resource guide | for mgmt developers |
| godoc API reference | for mgmt developers |
| prometheus guide | for everyone |
| puppet guide | for puppet sysadmins |
Questions:
Please ask in the community! If you have a well phrased question that might benefit others, consider asking it by sending a patch to the documentation FAQ section. I'll merge your question, and a patch with the answer!
Roadmap:
Please see: TODO.md for a list of upcoming work and TODO items. Please get involved by working on one of these items or by suggesting something else! Feel free to grab one of the straightforward #mgmtlove issues if you're a first time contributor to the project or if you're unsure about what to hack on!
Bugs:
Please set the DEBUG constant in main.go to true, and post the logs when you report the issue.
Bonus points if you provide a shell or OMV reproducible test case.
Feel free to read my article on debugging golang programs.
Patches:
We'd love to have your patches! Please send them by email, or as a pull request.
On the web:
Happy hacking!
