While ConanCenter is the default source for most open-source libraries, teams often add additional remotes for several reasons: conan remote — conan 1.66.0 documentation
After adding a remote, you can verify its status and order using the list command: conan remote list Use code with caution.
If you need to change a remote's URL later, use conan remote update : conan remote update my-repo https://example.com Use code with caution. Why Use Multiple Remotes? conan add remote
conan remote add internal-repo https://artifactory.com False Use code with caution. Advanced Configuration Options
Conan offers several flags to fine-tune how your remotes are handled, particularly in Conan 2.0+: While ConanCenter is the default source for most
: An optional boolean ( True or False ) to enable or disable SSL certificate verification. It defaults to True . Example: Adding a Private Repository
: Limits this remote to only be used for packages matching a specific pattern (e.g., zlib/* ), which is useful for security and preventing "dependency confusion" attacks. Managing the Remote List conan remote add internal-repo https://artifactory
To add a private Artifactory repository named "internal-repo" without strict SSL verification (common in internal testing environments):
: This flag allows you to add a remote even if the name already exists, effectively updating the existing entry instead of throwing an error.
: (Conan 2.x) A shorthand for skipping SSL verification.