Once you have finished entering the URL and move to another field, Artifactory automatically detects that the remote URL is on another instance of Artifactory and displays a dialog where you can configure the behavior of your smart remote repository. URL: Registry URL: h ttp:///artifactory/api/pypi/pypi-remote/ URL: Registry URL: For a remote repository:
PyPi repositories also require a registry URL which depends on whether the target is a local, remote or virtual repository on the target Artifactory instance. This gives you an opportunity to copy the artifact over from your remote repository cache to a local repository in case you need to maintain access to it. When viewing a cached artifact, Artifactory will indicate if the original artifact in the remote instance has been deleted. You can browse the contents of the repository in the remote Artifactory instance for all package types, even if none have been cached in your instance of Artifactory. By synchronizing properties, any changes to artifact properties in the remote instance are propagated to your cached instance of the artifact.
When you proxy a repository in another instance of Artifactory and cache an artifact downloaded from it, you may not be aware of changes that may have been made to the original artifact’s properties if they are done after you cache it.
Downloads are only reported through the proxy chain from the time this option is set, so the actual download statistics reported for an artifact may be different in the local Artifactory instance compared the numbers reported in the remote Artifactory instance.