In the previous sections, we built several packages in our computer, those packages are stored in the local cache, typically ~/.conan/data. Now, you might want to upload them to a conan server for later reuse on another machine, project, or for sharing them.
Conan packages can be uploaded to different remotes previously configured with a name and an URL. The remotes are just servers used as binary repositories that store packages by reference.
There are 3 possibilities to have a server where to upload packages:
- Conan server: You can run your own conan server that comes packaged with normal conan installers. Check Running your server for more information.
- Bintray: Bintray is a cloud platform that gives you full control over how you publish, store, promote, and distribute software. You can create binary repositories in Bintray to share conan packages or even create an organization. This is the recommended remote type for OSS packages. Check Using Bintray for more information.
- Artifactory: Artifactory is a binary repository manager for all major packaging formats, build tools and CI servers. It can host conan packages and manage them. It is the recommended remote type for professional package distribution. Check Artifactory documentation for more information.
If you are just evaluating conan, you can create an account on https://bintray.com and create a Conan repository, or you can run a conan server.
Conan official repositories are hosted in Bintray. These repositories are maintained by the Conan team. Currently there are two central repositories:
This repository has moderated, curated and well-maintained packages, and is the place where you can share your packages with the community. To share your package, you can upload it to your own (or your organization’s) repositories and submit an inclusion request to conan-center. Check conan-center guide for more information.
conan-transit: https://bintray.com/conan/conan-transit (DEPRECATED)
Deprecated. Contains mostly outdated packages some of them even not compatible with latest Conan versions, so its usage is discouraged. This repository only exists for backwards compatibility, it is not a default remote in the Conan client and will be completely removed soon. This repository is an exact copy of the old
server.conan.iorepository at June 11, 2017 08:00 CET. It’s a read-only repository, so you can only download hosted packages.
Conan comes with conan-center repository configured by default. Just in case you want to manually configure this repository you can always add it like this:
$ conan remote add conan-center https://conan.bintray.com
There are some popular community repositories that may be of interest for conan users to retrieve packages from. Some of these repositories are not affiliated with the Conan team.
bincrafters : https://bintray.com/bincrafters/public-conan
The Bincrafters team builds binary software packages for the OSS community. This repository contains a wide and growing variety of conan packages from contributors.
Use the following command to add this remote to Conan:$ conan remote add bincrafters https://api.bintray.com/conan/bincrafters/public-conan
conan-community : https://bintray.com/conan-community/conan
Created by Conan developers, it should be considered as an incubator to mature packages before contacting authors or including them in conan-center. This repository contains work-in-progress packages that may still not work and may not be fully featured.
Use the following command to add this remote to Conan:$ conan remote add conan-community https://api.bintray.com/conan/conan-community/conan
If you are working in a team, you probably want to use the same remotes everywhere: developer machines, CI. The
conan config install
command can automatically define the remotes in a conan client, as well as other resources as profiles. Have a look to the
conan config install command.