Hello,
First: Congratulations for 1.0.0, we do use it in production and it works as expected! Hooray \o/
I am trying to build caddy v1.0.1 using go get:
$ go version
go version go1.12.4 linux/amd64
$ cd `mktemp -d`
$ export GOPATH=`pwd`
$ export GO111MODULE=on
$ go get github.com/mholt/caddy/caddy@v1.0.1
go: finding github.com/mholt/caddy/caddy v1.0.1
go: finding github.com/mholt/caddy v1.0.1
go: downloading github.com/mholt/caddy v1.0.1
go: extracting github.com/mholt/caddy v1.0.1
go: github.com/mholt/caddy@v1.0.1: parsing go.mod: unexpected module path "github.com/caddyserver/caddy"
go: error loading module requirements
It worked fine for v1.0.0:
$ go get github.com/mholt/caddy/caddy@v1.0.0
go: finding github.com/mholt/caddy/caddy v1.0.0
go: finding github.com/mholt/caddy v1.0.0
go: downloading github.com/mholt/caddy v1.0.0
go: extracting github.com/mholt/caddy v1.0.0
go: finding github.com/jimstudt/http-authentication v0.0.0-20140401203705-3eca13d6893a
go: finding github.com/lucas-clemente/quic-go v0.10.2
go: finding github.com/kylelemons/godebug v0.0.0-20170820004349-d65d576e9348
go: finding github.com/hashicorp/go-syslog v1.0.0
go: finding github.com/klauspost/cpuid v1.2.0
go: finding github.com/naoina/toml v0.1.1
go: finding github.com/dustin/go-humanize v1.0.0
...
go: downloading golang.org/x/sys v0.0.0-20190228124157-a34e9553db1e
go: extracting golang.org/x/sys v0.0.0-20190228124157-a34e9553db1e
go: extracting golang.org/x/text v0.3.0
$ ls bin/caddy
bin/caddy
Is it related to KNOWN ISSUE
Building Caddy with plugins is difficult due to the repository move.
of 1.0.1?
Will it be fixed in > v1.0.1?
I assumed that go get
way with pinned tag/revision is the good way [tm] to build caddy from source, but is that approach really supported?
Regards,
Ĺukasz