➜  vcpkg-tool git:(localization-more) vcpkg help binarycaching                                                               
Vcpkg can cache compiled packages to accelerate restoration on a single machine or across the
network. By default, vcpkg will save builds to a local machine cache. This can be disabled by
passing `--binarysource=clear` as the last option on the command line.

Binary caching can be further configured by either passing `--binarysource=<source>` options to
every command line or setting the `VCPKG_BINARY_SOURCES` environment variable to a set of sources
(Ex: "<source>;<source>;..."). Command line sources are interpreted after environment sources.

Valid source strings:
  clear                           Removes all previous sources
  default[,<rw>]                  Adds the default file-based location.
  files,<path>[,<rw>]             Adds a custom file-based location.
  http,<url_template>[,<rw>[,<header>]]
                                  Adds a custom http-based location. GET, HEAD and PUT request are
                                  done to download, check and upload the binaries. You can use the
                                  variables 'name', 'version', 'sha' and 'triplet'. An example url
                                  would be
                                  'https://cache.example.com/{triplet}/{name}/{version}/{sha}'. Via
                                  the header field you can set a custom header to pass an
                                  authorization token.
  nuget,<uri>[,<rw>]              Adds a NuGet-based source; equivalent to the `-Source` parameter
                                  of the NuGet CLI.
  nugetconfig,<path>[,<rw>]       Adds a NuGet-config-file-based source; equivalent to the `-Config`
                                  parameter of the NuGet CLI. This config should specify
                                  `defaultPushSource` for uploads.
  nugettimeout,<seconds>          Specifies a nugettimeout for NuGet network operations; equivalent
                                  to the `-Timeout` parameter of the NuGet CLI.
  x-azblob,<url>,<sas>[,<rw>]     **Experimental: will change or be removed without warning** Adds
                                  an Azure Blob Storage source. Uses Shared Access Signature
                                  validation. URL should include the container path.
  x-gcs,<prefix>[,<rw>]           **Experimental: will change or be removed without warning** Adds a
                                  Google Cloud Storage (GCS) source. Uses the gsutil CLI for uploads
                                  and downloads. Prefix should include the gs:// scheme and be
                                  suffixed with a `/`.
  x-aws,<prefix>[,<rw>]           **Experimental: will change or be removed without warning** Adds
                                  an AWS S3 source. Uses the aws CLI for uploads and downloads.
                                  Prefix should include s3:// scheme and be suffixed with a `/`.
  x-aws-config,<parameter>        **Experimental: will change or be removed without warning** Adds
                                  an AWS S3 source. Adds an AWS configuration; currently supports
                                  only 'no-sign-request' parameter that is an equivalent to the
                                  '--no-sign-request parameter of the AWS cli.
  x-cos,<prefix>[,<rw>]           **Experimental: will change or be removed without warning** Adds
                                  an COS source. Uses the cos CLI for uploads and downloads. Prefix
                                  should include cos:// scheme and be suffixed with a `/`.
  interactive                     Enables interactive credential management for some source types

The `<rw>` optional parameter for certain strings controls whether they will be consulted for
downloading binaries and whether on-demand builds will be uploaded to that remote. It can be
specified as 'read', 'write', or 'readwrite'.
The `nuget` and `nugetconfig` source providers additionally respect certain environment variables
while generating nuget packages. The `metadata.repository` field will be optionally generated like:

    <repository type="git" url="$VCPKG_NUGET_REPOSITORY"/>
or
    <repository type="git"
                url="${GITHUB_SERVER_URL}/${GITHUB_REPOSITORY}.git"
                branch="${GITHUB_REF}"
                commit="${GITHUB_SHA}"/>

if the appropriate environment variables are defined and non-empty.

NuGet's cache is not used by default. To use it for every nuget-based source, set the environment
variable `VCPKG_USE_NUGET_CACHE` to `true` (case-insensitive) or `1`.

Based on your system settings, the default path to store binaries is "/Users/leanderSchulten/.cache/vcpkg/archives". This consults %LOCALAPPDATA%/%APPDATA% on Windows and $XDG_CACHE_HOME or $HOME on other platforms.
Extended documentation available at 'https://github.com/Microsoft/vcpkg/tree/master/docs/users/binarycaching.md'.

➜  vcpkg-tool git:(localization-more) vcpkg help binarycaching
vcpkg can cache compiled packages to accelerate restoration on a single machine or across the network. By default, vcpkg will save builds to a local machine cache. This can be disabled by passing "--binarysource=clear" as the last option on the command line.

Binary caching can be further configured by either passing "--binarysource=<source>" options to every command line or setting the `VCPKG_BINARY_SOURCES` environment variable to a set of sources (Example: "<source>;<source>;..."). Command line sources are interpreted after environment sources.

Valid source strings
clear: Removes all previous sources, including defaults
default[,<rw>]: Adds the default file-based location
files,<path>[,<rw>]: Adds a custom file-based location.
http,<url_template>[,<rw>[,<header>]]
Adds a custom http-based location. GET, HEAD and PUT request are done to download, check and upload the binaries. You can use the variables {name}, {version}, {sha} and {triplet}. An example url would be 'https://cache.example.com/{triplet}/{name}/{version}/{sha}'. Via the header field you can set a custom header to pass an authorization token.
nuget,<uri>[,<rw>]
Adds a NuGet-based source; equivalent to the "-Source" parameter of the NuGet CLI.
nugetconfig,<path>[,<rw>]
Adds a NuGet-config-file-based source; equivalent to the "-Config" parameter of the NuGet CLI. This config should specify "defaultPushSource" for uploads.
nugettimeout,<seconds>
Specifies a nuget timeout for NuGet network operations; equivalent to the "-Timeout" parameter of the  NuGet CLI.x-azblob,<url>,<sas>[,<rw>]
**Experimental: will change or be removed without warning** Adds an Azure Blob Storage source. Uses Shared Access Signature validation. URL should include the container path.
x-gcs,<prefix>[,<rw>]
**Experimental: will change or be removed without warning** Adds a Google Cloud Storage (GCS) source. Uses the gsutil CLI for uploads and downloads. Prefix should include the gs:// scheme and be suffixed with a "/".
x-aws,<prefix>[,<rw>]
**Experimental: will change or be removed without warning** Adds an AWS S3 source. Uses the aws CLI for uploads and downloads. Prefix should include s3:// scheme and be suffixed with a "/".
x-aws-config,<parameter>
**Experimental: will change or be removed without warning** Adds an AWS S3 source. Adds an AWS configuration; currently supports only 'no-sign-request' parameter that is an equivalent to the '--no-sign-request parameter of the AWS CLI.
x-cos,<prefix>[,<rw>]
**Experimental: will change or be removed without warning** Adds an COS source. Uses the cos CLI for uploads and downloads. Prefix should include cos:// scheme and be suffixed with a "/".
interactive: Enables interactive credential management for some source types

The "<rw>" optional parameter for certain strings controls whether they will be consulted for downloading binaries and whether on-demand builds will be uploaded to that remote. It can be specified as "read", "write", or "readwrite".

The "nuget" and "nugetconfig" source providers additionally respect certain environment variables while generating nuget packages. The "metadata.repository" field will be optionally generated like:

<repository type="git" url="$VCPKG_NUGET_REPOSITORY"/>
or
<repository
 type="git"
 url="${GITHUB_SERVER_URL}/${GITHUB_REPOSITORY}.git"
 branch="${GITHUB_REF}"
 commit="${GITHUB_SHA}"/>

if the appropriate environment variables are defined and non-empty.

NuGet's cache is not used by default. To use it for every nuget-based source, set the environment variable "VCPKG_USE_NUGET_CACHE" to "true" (case-insensitive) or "1".
Based on your system settings, the default path to store binaries is "/Users/leanderSchulten/.cache/vcpkg/archives". This consults %LOCALAPPDATA%/%APPDATA% on Windows and $XDG_CACHE_HOME or $HOME on other platforms.
Extended documentation available at 'https://github.com/Microsoft/vcpkg/tree/master/docs/users/binarycaching.md'.