You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running golang.org/x/pkgsite/cmd/pkgsite locally to see documentation for a package I'm working on has been a generally great experience, but I've noticed that pkgsite is trying to fetch information from https://deps.dev for my private packages, and I'd like to avoid those requests.
For example, if I make go.mod
module example.com/demomodule
go 1.19
and demo.go
package demomodule
funcThisIsAFunction() {}
When I run golang.org/x/pkgsite/cmd/pkgsite from that directory, I can see rendered docs when I go to http://localhost:8080/example.com/demomodule in my browser, but I also see failed requests to deps.dev:
$ pkgsite2022/09/16 09:17:27 Info: Listening on addr http://localhost:80802022/09/16 09:17:33 Info: FetchDataSource: fetching example.com/demomodule@latest2022/09/16 09:17:33 Info: FetchDataSource: fetched example.com/demomodule@latest in 4.04575ms with error <nil>2022/09/16 09:17:33 Warning: fetching url from deps.dev: Get "https://deps.dev/_/s/go/p/example.com%2Fdemomodule/v/v0.0.0/exists": context deadline exceeded
#47463 suggests other external sources might be called in the future, so would it make sense to have a configurable pattern (similar to how GOPRIVATE/GONOPROXY/GONOSUMDB work?) to exclude certain packages from being looked up in external resources?
The text was updated successfully, but these errors were encountered:
Running
golang.org/x/pkgsite/cmd/pkgsite
locally to see documentation for a package I'm working on has been a generally great experience, but I've noticed that pkgsite is trying to fetch information from https://deps.dev for my private packages, and I'd like to avoid those requests.For example, if I make
go.mod
and
demo.go
When I run
golang.org/x/pkgsite/cmd/pkgsite
from that directory, I can see rendered docs when I go to http://localhost:8080/example.com/demomodule in my browser, but I also see failed requests to deps.dev:#47463 suggests other external sources might be called in the future, so would it make sense to have a configurable pattern (similar to how
GOPRIVATE/GONOPROXY/GONOSUMDB
work?) to exclude certain packages from being looked up in external resources?The text was updated successfully, but these errors were encountered: