Why do you need a local version of hex? If what you need are private packages, what about using the organizations feature from hex.pm? It’s paid, but it could pay out all the effort, and you also would be helping the community to grow!
@kelvinst A local version of Hex would be useful in the face of Hex connectivity issues. We’re unable to currently deploy because of Hex image pull connectivity errors, and a local Hex would allow one to bypass that externality. Private Nexus servers are extraordinarily common in the Java world, and things like private NPM servers exist in JS.
Yeah, I know, I just asked to know the real reason behind creating a local version of hex. About not being up to you: another option would be to use path dependencies instead of hex.pm ones, or even using umbrella projects. The other option is what you have tried, but I never done it so I can’t help unfortunately.