Configuration

This section shows you how to configure the following for the Package Manager:

• Network configuration: get around a firewall and set up a proxy server.
• Scoped registry authentication: create and provide Package Manager with an authentication token for any scoped package registry servers that require it.
• Customize the global cache ___location: override the ___location of the global cache folders.
• Customize the asset package cache ___location: override the ___location of the asset packageA collection of files and data from Unity projects, or elements of projects, which are compressed and stored in one file, similar to Zip files, with the .unitypackage extension. Asset packages are a handy way of sharing and re-using Unity projects and collections of assets. Customize the asset package cache ___location: override the ___location of the asset packageA collection of files and data from Unity projects, or elements of projects, which are compressed and stored in one file, similar to Zip files, with the .unitypackage extension. Asset packages are a handy way of sharing and re-using Unity projects and collections of assets. More info
  See in Glossary cache folder.
• Using private repositories with HTTPS Git URLs: use a Git credential helper to access private repositories over HTTPS.
• Using passphrase-protected SSH keys with SSH Git URLs: use an authentication agent to access private repositories over SSH.

In addition, you can find the ___location of the Package Manager configuration files under Configuration files.

Configuration files

Package Manager supports two configuration files: a global configuration file and a user configuration file. Both of these files use the TOML format and they appear in different locations:

• Global configuration files apply to all users on the machine. For example, you can define additional SSL certificate authorities when setting up a proxy server for the entire machine.
• User configuration files apply to a single user. For example, you can set up authentication tokens to use for custom package registry servers that you access with scoped registries. These tokens authenticate a specific user account.

Global configuration file ___location

Package Manager uses a global configuration file named upmconfig.toml. This file isn’t created when you install the Unity Hub or Editor, but you can create it in the following ___location if you need to customize your configuration:

You can define a custom ___location that overrides the default ___location for your configuration file. To do this, create a UPM_GLOBAL_CONFIG_FILE environment variable and set its value to the absolute path of your configuration file, including the file name.

User configuration file ___location

Package Manager uses a user configuration file named .upmconfig.toml. This file isn’t created when you install the Unity Hub or Editor, but you can create it in the following ___location if you need to customize your configuration:

You can define a custom ___location that overrides the default ___location for your configuration file. To do this, create a UPM_USER_CONFIG_FILE environment variable and set its value to the absolute path of your configuration file, including the file name.