different configurations. • Automated/remote package generation in Travis/Appveyor server with distributed builds in CI jobs for big/slow builds. • Docker: Automatic generation of packages for several Running and deploying packages Executables and applications including shared libraries can be also distributed, deployed and run with conan. This might have some advantages compared to deploying with other 10 Can I upload closed source libraries? Yes. As long as the resulting binary artifact can be distributed freely and free of charge, at least for educational and research purposes, and as long as you comply

different configurations. • Automated/remote package generation in Travis/Appveyor server with distributed builds in CI jobs for big/slow builds. • Docker: Automatic generation of packages for several Running and deploying packages Executables and applications including shared libraries can also be distributed, deployed and run with Conan. This might have some advantages compared to deploying with other attribute_checker that has been packaged with Conan sources for several versions (although it is distributed with Conan still, it is no longer maintained and we may remove it in the future, so we encourage

different configurations. • Automated/remote package generation in Travis/Appveyor server with distributed builds in CI jobs for big/slow builds. • Docker: Automatic generation of packages for several Running and deploying packages Executables and applications including shared libraries can also be distributed, deployed and run with Conan. This might have some advantages compared to deploying with other attribute_checker that has been packaged with Conan sources for several versions (although it is distributed with Conan still, it is no longer maintained and we may remove it in the future, so we encourage

different configurations. • Automated/remote package generation in Travis/Appveyor server with distributed builds in CI jobs for big/slow builds. • Docker: Automatic generation of packages for several Running and deploying packages Executables and applications including shared libraries can be also distributed, deployed and run with conan. This might have some advantages compared to deploying with other 10 Can I upload closed source libraries? Yes. As long as the resulting binary artifact can be distributed freely and free of charge, at least for educational and research purposes, and as long as you comply

different configurations. • Automated/remote package generation in Travis/Appveyor server with distributed builds in CI jobs for big/slow builds. • Docker: Automatic generation of packages for several Running and deploying packages Executables and applications including shared libraries can be also distributed, deployed and run with conan. This might have some advantages compared to deploying with other 10 Can I upload closed source libraries? Yes. As long as the resulting binary artifact can be distributed freely and free of charge, at least for educational and research purposes, and as long as you comply

different configurations. • Automated/remote package generation in Travis/Appveyor server with distributed builds in CI jobs for big/slow builds. • Docker: Automatic generation of packages for several Running and deploying packages Executables and applications including shared libraries can be also distributed, deployed and run with conan. This might have some advantages compared to deploying with other 10 Can I upload closed source libraries? Yes. As long as the resulting binary artifact can be distributed freely and free of charge, at least for educational and research purposes, and as long as you comply

different configurations. • Automated/remote package generation in Travis/Appveyor server with distributed builds in CI jobs for big/slow builds. • Docker: Automatic generation of packages for several Running and deploying packages Executables and applications including shared libraries can be also distributed, deployed and run with conan. This might have some advantages compared to deploying with other 10 Can I upload closed source libraries? Yes. As long as the resulting binary artifact can be distributed freely and free of charge, at least for educational and research purposes, and as long as you comply

Rest API and generic repositories to host any artifact. • The conan_server is a small server distributed together with the Conan client. It is a simple open-source imple- mentation, it provides the basic different configurations. • Automated/remote package generation in Travis/Appveyor server with distributed builds in CI jobs for big/slow builds. • Docker: Automatic generation of packages for several Running and deploying packages Executables and applications including shared libraries can also be distributed, deployed and run with Conan. This might have some advantages compared to deploying with other

Rest API and generic repositories to host any artifact. • The conan_server is a small server distributed together with the Conan client. It is a simple open-source imple- mentation, it provides the basic different configurations. • Automated/remote package generation in Travis/Appveyor server with distributed builds in CI jobs for big/slow builds. • Docker: Automatic generation of packages for several Running and deploying packages Executables and applications including shared libraries can also be distributed, deployed and run with Conan. This might have some advantages compared to deploying with other

Rest API and generic repositories to host any artifact. • The conan_server is a small server distributed together with the Conan client. It is a simple open-source imple- mentation, it provides the basic Documentation, Release 1.27.1 • Automated/remote package generation in Travis/Appveyor server with distributed builds in CI jobs for big/slow builds. • Docker: Automatic generation of packages for several Running and deploying packages Executables and applications including shared libraries can also be distributed, deployed and run with Conan. This might have some advantages compared to deploying with other