Hex Limitations in Artifactory

The following are the limitations of Hex in Artifactory:

Mix Client:
- Single Repository Limitation: The Mix client allows only one repository to point to repo.hex.pm. As a result, you can only set one Artifactory endpoint as the default repository that connects to the public hex.pm registry.
- Repository Naming: The name of your self-hosted Hex repository in the Mix client must exactly match the full URL of the Artifactory remote repository.
Hex Server:
- Private Package Support: Self-hosted Hex servers do not support private organizations or private packages. This feature is only available through the public hex.pm registry, which offers private hosted repositories.
Hex Local Repository:
- We currently support using local repositories for storing first-party (internal) and second-party (partner) packages.
- parsing any info related to docs, tests, etc.; from mix.exs is not supported.
- mix hex.publish command to publish packages to local repository is not supported.
  Workaround:Deploy Hex Packages via API to local repository.
- deploying packages under any other directory except tarballs is not supported. To learn more, refer to Hex Repository Layout and Permission.
Hex Remote Repository: We currently support using remote repositories for caching third-party packages from registries, such as hex.pm.
Repository Browsing: Artifactory does not support browsing Hex remote registries. The artifact tree only shows packages explicitly pulled into Artifactory, not the contents of the remote registry.
Hex Virtual Repository: A single Mix client can link to only one Hex virtual repository.