search

bower / registry

The Bower registry
https://registry.bower.io/packages
MIT License
292 stars 66 forks source link

Registry is no longer accepting valid but private / enterprise git endpoints #84

Closed rayshan closed 10 years ago

rayshan commented 10 years ago

This patch uses git ls-remote to validate git endpoints: https://github.com/bower/registry/pull/78

However we won't be able to validate private / enterprise packages. E.g. coreComponents, currently in the registry:

> git ls-remote git://github.paypal.com/HotPocket/Settings.git

fatal: unable to connect to github.paypal.com:
github.paypal.com: Name or service not known

I think we need to revert https://github.com/bower/registry/pull/78, decide whether we will accept private git endpoints, and document this for the community.

cc @patrickkettner

patrickkettner commented 10 years ago

> The issue is that we must ensure the repo you are trying to register is public

patrickkettner commented 10 years ago

that was by design. there are a few broken packages in the repo, currently, that are not even valid. My understanding was that anything like this would be just put into either a private bower instance or referenced by url in the bower.json

why would we want to have private repos in the public bower?

rayshan commented 10 years ago

Ok got it, thanks. I think I misunderstood @satazor's last comment in that issue. I'll make sure docs on bower.io reflect this and provide some tips regarding running a private bower registry.

patrickkettner commented 10 years ago

sounds great!