This plugin breaks a caddy build with the following message:

.go/pkg/mod/github.com/restic/[email protected]/setup.go:19:16: undefined: restserver.Server
.go/pkg/mod/github.com/restic/[email protected]/setup.go:42:19: undefined: restserver.NewHandler

The issue is maybe related to caddy requiring Go modules to build since its 1.0.0. Introducing modules support is quite easy, simply run go mod init github.com/restic/caddy in the root of your repository and commit go.sum and go.mod that are created by the aforementioned command.

I've roughly looked at the process:

• We need to open a PR for caddy to correct the URL https://github.com/mholt/caddy/blob/7b5efb5d7581e7c6f04f000369708f5cf25e10f4/caddyhttp/httpserver/plugin.go#L498
• Register the plugin
• Tag a release so that the website includes it as an option

The release 1.0.3 of caddy does not with github.com/restic/caddy, because the commit d755491 is missing in the latest release.

I might be something incorrectly, but here's my Caddy config file.

https://example.com/backups/repo1 {

	tls {
        	dns cloudflare
	}

	basicauth user pass {
        	/
	}

	restic / /home/backups/repo1

}



https://example.com/backups/repo2 {

	tls {
        	dns cloudflare
	}

	basicauth user pass {
        	/
	}

	restic / /home/backups/repo2

}


https://example.com/backups/repo3 {

	tls {
        	dns cloudflare
	}

	basicauth user pass {
        	/
	}

	restic / /home/backups/repo3

}

I can access all virtual paths, however it only writes to the physical path of the last site configured with restic.

So I can connect to repo1, repo2, and repo3 fine, but it all attempts to save under repo3.

(I know I could change this myself in a jiffy -- I'm just filing issues for as many plugins as I can, then I can come back and make a commit if someone doesn't beat me to it.)

Caddy's import path (and Go module name) has changed from

github.com/mholt/caddy

to

github.com/caddyserver/caddy

Unfortunately, Go modules are not yet mature enough to handle a change like this (see https://golang.org/issue/26904 - "haven't implemented that part yet" but high on priority list for Go 1.14) which caught me off-guard. Using Go module's replace feature didn't act the way I expected, either. Caddy now fails to build with plugins until they update their import paths.

I've hacked a fix into the build server, so downloading Caddy with your plugin from our website should continue working without any changes on your part, for now. However, please take a moment and update your import paths, and do a new deploy on the website, because the workaround involves ignoring module checksums and performing a delicate recursive search-and-replace.

I'm terribly sorry about this. I did a number of tests and dry-runs to ensure the change would be smooth, but apparently some unknown combination of GOPATH, Go modules' lack of maturity, and other hidden variables in the system or environment must have covered up something I missed.

This bash script should make it easy (run it from your project's top-level directory):

find . -name '*.go' | while read -r f; do
	sed -i.bak 's/\/mholt\/caddy/\/caddyserver\/caddy/g' $f && rm $f.bak
done

We use this script in the build server as part of the temporary workaround.

Let me know if you have any questions! Sorry again for the inconvenience.

I didn't find a way to use the option --append-only from the last rest-server in this plugin.
Having feature parity between server and plugin would be great.