Can devpi proxy multiple remote respositories?
Our corp standard requires that all in-house build products (notably including .whl files) must be housed in Artifactory. We can resolve them from there via Artifactory's PyPi facade (read-only). But we don't want to have to check in external packages (from public PyPi) into Artifactory--and it makes no sense to do so. Can an index in devpi have, as a base, both public/pipi and an additional external, read-only repo, and serve as proxy for both?
Hi! On 12 Oct 2015, at 17:59, Sam Reynolds wrote:
Can an index in devpi have, as a base, both public/pipi and an additional external, read-only repo, and serve as proxy for both?
Not yet. There are plans to allow that and the first steps have been made, but it's not possible at this time. Regards, Florian Schulze
Bummer. It does exactly what we need for dev, but this would certainly simplify working with our mandated release chain. I guess we'll have to "pip install" using --index-url and --extra-index-url. On Monday, October 12, 2015 at 9:59:16 AM UTC-6, Sam Reynolds wrote:
Our corp standard requires that all in-house build products (notably including .whl files) must be housed in Artifactory. We can resolve them from there via Artifactory's PyPi facade (read-only). But we don't want to have to check in external packages (from public PyPi) into Artifactory--and it makes no sense to do so.
Can an index in devpi have, as a base, both public/pipi and an additional external, read-only repo, and serve as proxy for both?
participants (2)
-
Florian Schulze -
Sam Reynolds