The public bower registry does not contain any actual binary packages; it is a simple key-value store pointing from a package name to its equivalent Git repository.
Since most of the packages are hosted in GitHub, you will want to create a Remote Repositories which serves as a caching proxy for github.com. If necessary, you can do the same for bitbucket.org or any other remote repository you want to access.
Working with Bitbucket?
If your packages are hosted on Bitbucket (formerly Stash), you need to ensure that the Bitbucket Archive Plugin is installed on your Bitbucket server.
Artifacts (such as tar.gz files) requested from a remote repository are cached on demand. You can remove downloaded artifacts from the remote repository cache, however you can not manually deploy artifacts to a remote repository.
To define a remote repository to proxy github.com as well as the public Bower registry follow the steps below:
Create a new remote repository in the Administration module, under Repositories | Repositories | Remote, click "New Remote Repository" and set Bowerto be its Package Type
Set the Repository Key value, and enter
https://github.comin the URL field as displayed below.
In the Bower Settings section, select GitHub as the Git Provider.
Finally, click "Save & Finish"
Bower Registry URL
Usually, you will point the Bower Registry URL field at the public registry as displayed above.
However, if you are using a private bower registry or a remote Artifactory instance, simply set the same URL as configured in URL field.
Bower have changed their registry URL from the default configured in Artifactory. In order to resolve from the public registry, set the Registry URL tohttps://registry.bower.io.