Instead of using `godep path`, we can simply set the GOPATH directly to
point to the Godeps/_workspace. We can still use `godep` to manage the
dependencies on the Godeps/ tree, but we don't need to have it available
for straight builds from git.
v2: Rebased and moved to inside kube::setup_go_environment() function.
Tested:
- Built it without godep in $PATH:
$ hack/build-go.sh
- Ran unit tests without godep in $PATH:
$ hack/test-go.sh
- Retested after rebase.
Signed-off-by: Filipe Brandenburger <filbranden@google.com>
While the linux dependency is obvious with a moment's thought, some
users (especially on *nix) might plow ahead before realizing their
system isn't supported. This adds a requirements section and points
users in the direction of guides more likely to work for them.
Building kubecfg is required for kubecfg.sh. kubecfg.sh will warn
of this if it hasn't been built, but it's a better user experience
to make people explicitly aware of all required steps.
The project README is getting quite large mainly because of all
the getting started guides embedded in the README.
Create the docs/getting-started-guides directory and relocate all
getting started guides. Update the README to link to each getting
started guide.
As I read through it I wanted to wordsmith a bit, which lead to reordering
some to read sort of top-down. There were a couple things I thought were wrong
(pod name should be a subdomain) and a few things I think we can make more
concise. I also added examples and clarified implications.