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 Store cache location: override the location of the Asset StoreA growing library of free and commercial assets created by Unity and members of the community. Offers a wide variety of assets, from textures, models and animations to whole project examples, tutorials and Editor extensions. More info
  See in Glossary package cache folder.

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:

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: