-
Notifications
You must be signed in to change notification settings - Fork 131
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
It doesn't fallback to public packages #179
Comments
I experienced the same issue. I got around it by adding the public bower repository to the .bowerrc config file, details in Bower config. E.g.
|
Hi, I got the same issue, it was working very well, then it fails to |
Same issue here. Just noticed it today. |
Something might have changed in the hosting environment of the public registry since /packages/ doesn't resolve to the registered route /packages. Removing the trailing / in the config worked for me. |
Same over here. The solution @ow-- mentions (remove the traling / in the private bower config) is working for me too. |
@Hacklone Can you merge this ? Several people encountered the same problem :) |
I copy-pasted the example in http://hacklone.github.io/private-bower/#config-file and it had the trailing |
this was already fixed in README.MD but not on gh-pages. This is the reason why it is a problem: Hacklone#179 (comment)
removed "/" from example config, which causes #179
I installed private-bower following this post, I used sample configuration to start the private bower, it runs well but it doesn't fallback to public packages.
When I search a package that doesn't exist in my private registry, it just return "No results".
The text was updated successfully, but these errors were encountered: