Add support for self hosted deployments

[alexkappa]

resolves #16

For self hosted deployments of gopkg, the -domain flag should be used to specify the domain you want to use. For example go.mysite.com.

Now your github repositories are go get-able with a custom domain. go get go.mysite.com/user/pkg.v0.

To make the import path more concise, you could specify your github username using the -github flag. The import path go.mysite.com/pkg.v0 would resolve to github.com/user/pkg instead of github.com/go-pkg/pkg.

[gtrevg]

Nice. I was just needing that feature.

[GeertJohan]

Althought this is probably a nice feature for this piece of software to have, I would not recommend running your own version of gopkg.in. The gopkg.in service has a redundant setup with servers in multiple locations. You never know where you'll be in 10 years, and if your server/vps is still running stable at that time. Stopping a self-hosted gopkg service will break code using it.

Still though, a nice feature. I've commented inline with one thing I would change.

[gtrevg]

Any update on incorporating this feature into the main gopkg project? I'm looking to build upon this idea by adding the ability to connect to private github server that requires a login to access any of the repo's content. It would be nice to work off of the main project, rather than a fork of the main project.

Thanks

[nathany]

https://github.com/azul3d/semver is a fork/rewrite for self-hosted use. Might do the trick.

[emidoots]

@nathany @gtrevg not a fork at all. It was written from the ground up and has different goals than gopkg.in (they're independent projects). see here for more details on that.

[gtrevg]

Thanks for the notes about the semver project. I'll definitely check it out. It looks like it may solve the problem I was facing. Thanks!

[niemeyer]

This is not supposed to be base for similar tools, and it's been clearly standing here for too long. For future generations, please feel free to fork the tool and play with it as desired. :)