I’ve personally not seen one for artifactory but it is extensible in mix.deps as I recall, you’d just specify your own SCM module (maybe a manager too?) and you can use it to specify dep locations too as I recall. I’m unsure on the details as I’ve not made one, but maybe @josevalim or someone will pop in to clarify how with links to documentation?

Artifactoy has had an open jira item since about 2016 to support this, that appears to now be on the 2021 roadmap.

Additionally, I was able to host elixir client libs in a generic artifactory repo by using a modified version of the mix hex.registry build that my much-more-experienced co-worker helped me with. It borrows from the source of mix hex.registry build but uses the existing metadata files and modifies them instead of re-writing them.

Pipeline:

• create directory structure outlined by hexpm here
• download meta data files from the artifactory repo (names, versions, packages/*)
• add new .tar files to tarballs/
• use our custom mix task (containerized in a CI pipeline) to update the metadata files
• upload new .tar files and updated metadata files

For some reasons - such as auditing and network requirement, etc. - having Elixir support in such artifact/package management software is often wanted, even elixir package is just source code package. Note that go is adopting “package” system and Artifactory and Nexus support Go as well..

These are tickets for Elixir, for the reference.

• Artifactory: Jira
• Nexus: What Happened To issues.sonatype.org? - Documentation

For related discussion and resource:

https://github.com/wojtekmach/mini_repo