Hex Repository Prerequisites

JFrog Artifactory Documentation

Products
JFrog Artifactory
Content Type
User Guide
ft:sourceType
Paligo

The Hex package manager is unique as it uses protobuf encoding for efficient binary sizing and performance. This means that every Hex package is encrypted by the server and decrypted by the client/proxy server using an RSA public key.

Generate and upload RSA key pair to Artifactory: These RSA keys will be assigned to your Hex repositories to encode the content for transfer to the Mix client.

For Artifactory to support the following you must meet the above prerequisite before proceeding with creating repositories:

  • Provide the Hex upstream registry public key

    This is entered during the remote repository creation and used to decrypt the package content being downloaded from the upstream registry to Artifactory.

    Note

    When using the Hex.pm public registry we auto-populate this value for you. For self-hosted Hex servers, you are required to provide the public key manually in the repository setup.

  • Place the Artifactory public key within your Hex Project

    This is required according to the Mix client specification to allow the Mix client to validate and decrypt the package content from Artifactory.

    Note

    We have streamlined this process by providing a quick download code snippet as part of our Set Me Up instructions.