Go modules daily use

1. initialization
go mod init
2. Go Proxy
Due to limited access to domestic and foreign networks , Usually we will cooperate Go Proxy Use , To prevent the use of go get It takes too long to get the source code package or cannot be downloaded ：
go env -w GOPROXY=https://goproxy.cn
3.go.mod
Every time go get Will be modified at the same time go.mod and go.sum file .

These two files are the main basis for downloading dependent packages .go.mod Be similar to PHP Medium composer.json , and go.sum It is composer.lock.

Open view go.mod Source code ：

go.mod

module github.com/summerblue/goblog

go 1.15

require (
    github.com/gorilla/mux v1.7.4
    github.com/julienschmidt/httprouter v1.3.0 // indirect
)

A few parameters ：

module —— our goblog stay Go Module It's one of them Module ;
go —— Version requirements are specified , The minimum 1.15
require —— It is the dependency of the project
4. Empty Go Modules cache
go clean -modcache

5. Download dependency
go mod download
6. all Go Modules command
command effect
go mod init Generate go.mod file
go mod download download go.mod All dependencies specified in the file
go mod tidy Sort out existing dependencies
go mod graph Look at the existing dependency structure
go mod edit edit go.mod file
go mod vendor All dependencies of the export project depend on vendor Catalog
go mod verify Verify that a module has been tampered with
go mod why See why you need to rely on a module