0
0
mirror of https://github.com/tj/n.git synced 2024-11-21 18:48:57 +01:00

Tighter and consistent wording

This commit is contained in:
John Gee 2021-04-25 11:26:46 +12:00
parent b558b66de1
commit fdff491f88
2 changed files with 5 additions and 7 deletions

View File

@ -215,11 +215,9 @@ The most common example is from users in China who can define:
export N_NODE_MIRROR=https://npm.taobao.org/mirrors/node
If the custom mirror requires authentication you can [url encode](https://urlencode.org/) the credentials into the URL:
If the custom mirror requires authentication you can add the [url-encoded](https://urlencode.org) username and password into the URL. e.g.
https://username:password@host:port/path
The encoding is especially important when the username or password contains special characters.
export N_NODE_MIRROR=https://encoded-username:encoded-password@host:port/path
There is also `N_NODE_DOWNLOAD_MIRROR` for a different mirror with same layout as the default <https://nodejs.org/download>.

View File

@ -6,11 +6,11 @@ Under the hood, `n` uses `curl` or `wget` for the downloads. `curl` is used if a
You can define the proxy server using an environment variable, which is read by multiple commands including `curl` and `wget`:
export https_proxy='http://host:port/path'
export https_proxy='https://host:port/path'
If your proxy requires authentication you can [url-encode](https://urlencode.org) the username and password in the URL. e.g.
If your proxy requires authentication you can add the [url-encoded](https://urlencode.org) username and password into the URL. e.g.
export https_proxy='http://user:password@host:port/path'
export https_proxy='https://encoded-user:encoded-password@host:port/path'
If you have defined a custom node mirror which uses http, then you would define `http_proxy` rather than `https_proxy`.