goproxy

Objective: with the release of go1.11, go has introduced the Go module to solve the dependency management problem, the Go module is integrated into the native go cmd, but if your code base is in $gopath, the module function of go1.11 is not enabled by default and wants to Open is also very simple, with an environment variable to open go module: export GO111MODULE=on . About $GOPROXY When we use go, go defaults to download the dependent depende

Title: "Go 1.11 module"Date: 8-8-10-26t23: 50: 56 + 08: 00Draft: false---Go 1.11 module Introduction Go 1.11 released a new mode to manage the dependent libraries of Go programs. This method is different fromvendorModel. It provides the following important features: It is easier to work without gopath (I understand that gopath gradually fades out, And gopath once left a lot of pitfalls for beginners of golang) Use$GOPATH/pkg/modTo storego modCache file to improvego getSpeed Optional$GOPROXYI

languages. At the same time, the design must work well without assuming such a proxy or registry. We want to eliminate vendor directories. They were introduced for reproducibility and availability, but we are now having better mechanisms. Reproducibility is handled by proper versioning, and availability are handled by caching proxies. Proxy Server An independent developer or company will need to update the Golang dependency Library from a proxy server instead of the original address. Some of th

list command will be dependent on the dependency of the automatic generation of require statements. The official recommendation is to maintain this file regularly, keeping dependencies clean. For domestic users, manual maintenance of this file is inevitable, because you need to golang.org/x/text replace the github.com/golang/text AH. No need to replace the dependency in the hack way as before, GOPATH I still have the old thinking in the beginning, actually want to replace the download cache of

1. Go commands: Godoc-http: 8080 // obtain the official website documentation locally Go get // obtain the remote resource package Go run // run the program directly Go build // test compilation and check for any compilation errors Go install // compile the package file and compile the entire program 2. Go environment variables and working directory * Bin: stores the executable files generated after compilation. * PKG: stores the compiled package files. * SRC: stores the project sourc