Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support more registries #34

Open
3 tasks
victorb opened this issue May 11, 2019 · 0 comments
Open
3 tasks

Support more registries #34

victorb opened this issue May 11, 2019 · 0 comments

Comments

@victorb
Copy link
Member

victorb commented May 11, 2019

Currently, Open-Registry acts like a npm proxy and exposes the archive we're currently building of that proxy.

However, npm is not the only package registry run by for-profit entities. Some others on the top of my mind are Packagist (composer/PHP) and Docker Hub. These registries should also, similar to the npm registry, be developed for and by the community, rather than being controlled by centralized organizations.

Currently, the architecture of the application (basically, just a proxy that caches packages in IPFS) makes it very easy to develop compatability with new packages. I'd like to rip out the parts which does the heavy-lifiting into it's own library, then we can add proxies as needed.

The order of implementing these would be the following:

  • Extract out proxy-caching logic into it's own lib
  • Compatible with Packagist
  • Compatible with Docker Hub

Is there other registries run by for-profit companies that you think Open-Registry should provide an alternative to? Is the idea of having Open-Registry being a general package registry spreading our work to thin?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant