* Doc update to configure upstream proxy to fetch modules from a Go modules repository * review suggestions
1.4 KiB
title, description, weight
| title | description | weight |
|---|---|---|
| Configuring Upstream Proxy to use an Upstream Go Modules Repository | How to Configure Athens to Fetch Missing Modules From an Upstream Module Repository Like GoCenter, or Another Athens Server | 1 |
By default, Athens fetches module code from an upstream VCS like github.com, but this can be configured to use a Go modules repository like GoCenter or another Athens Server.
-
Create a filter file (e.g
/usr/local/lib/FilterForGoCenter) with letterD(stands for "direct access") in first line. For more details, please refer to documentation on - Filtering Modules# FilterFile for fetching modules directly from upstream D -
If you are not using a config file, create a new config file (based on the sample config.dev.toml) and edit values to match your environment). Additionally in the current or new config file, set the following parameters as suggested:
FilterFile = "/usr/local/lib/FilterForGoCenter" GlobalEndpoint = "https://<url_to_uptream>" # To use GoCenter for example, replace <url_to_upstream> with gocenter.io -
Restart Athens specifying the updated current or new config file.
/proxy -config_file <path-to updated current or new configfile> -
Verify the new configuration using the steps mentioned in ("Try out Athens" document)[/try-out], and go through the same walkthrough example.