Awesome

private-bower

The ultimate private bower server.

Twitter: <a href="https://twitter.com/private_bower">@private_bower</a>, <a href="https://twitter.com/hashtag/private_bower?src=hash">#private_bower</a>

• Features
• Features to come
• Installation
• Parameters
• Config file
• Usage
  • Web interface
  • Project
  • List packages
  • Search packages
  • Register package
  • Register packages
  • Remove package
  • Remove packages
  • Restart server
  • Refresh caches
  • Authentication
  • Log4js configuration examples
• License
• Tips for usage
• Contributing

Features

• Register private packages
• Fallback to public packages
• Cache public registry
• Cache public git repositories
• Cache public svn repositories
• Web UI with package details
• Web UI package management
• Blacklist public packages
• Whitelist public packages

Installation

Install

npm install -g private-bower

Run

private-bower

Run with config file specified

private-bower --config ./myBowerConfig.json

If there's no private package with requested package name the servers calls through to the public bower registry.

Parameters

Config file

Must be a valid JSON

{
    "registryFile": "./bowerRepository.json",
    "timeout": 144000,
    "server": {
        "port": 5678,
        "hostName": null,
        "siteBaseUrl": null
    },
    "public": {
        "disabled": false,
        "registry": "http://bower.herokuapp.com/packages",
        "registryFile": "./bowerRepositoryPublic.json",
        "whitelist": [],
        "blacklist": []
    },
    "authentication": {
        "enabled": false,
        "key": "password"
    },
    "repositoryCache": {
        "cachePrivate": false,
        "git": {
            "enabled": false,
            "cacheDirectory": "./gitRepoCache",
            "host": "localhost",
            "port": 6789,
            "protocol": "git",
            "publicAccessURL": null,
            "refreshTimeout": 10,
            "refreshDisabled": false
        },
        "svn": {
            "enabled": false,
            "cacheDirectory": "./svnRepoCache",
            "host": "localhost",
            "port": 7891,
            "protocol": "svn",
            "publicAccessURL": null,
            "refreshTimeout": 10,
            "refreshDisabled": false
        }
    },
    "proxySettings" : {
        "enabled": false,
        "host": "proxy",
        "username": "name",
        "password": "pass",
        "port": 8080,
        "tunnel": false
    },
    "log4js" : {
        "enabled": false,
        "configPath": "log4js.conf.json"
    }
}

Usage

Web interface

Convenient way for viewing your packages in a browser. The web interface will only list your private packages, it will not list the public packages if you have a public registry enabled. However, when searching for packages in bower, the public ones will show up just fine.

http://localhost:5678/

Project

Within your project, you will need to create a .bowerrc file containing the URL of your private bower server:

{
  "registry": "http://yourPrivateBowerRepo:5678",
  "timeout": 300000
}

If you are using private bower with server.siteBaseURL option, you need to add the same path the registry url in your .bowerrc file:

Config

{
  "server": {
    "port": 6789,
    "hostName": "yourPrivateBowerRepo",
    "setBaseURL": "/my-private-bower"
  }
}

.bowerrc

{
  "registry": "http://yourPrivateBowerRepo:6789/my-private-bower",
  "timeout": 300000
}

List packages

GET

bower-server:5678/packages

Search packages

bower search [packageName]

Register package

bower register [packageName] [gitRepo]

or POST

bower-server:5678/packages

{ "name": "package-name", "url": "git://repoPath" }

or POST

bower-server:5678/packages/<package name>

{ "url": "git://repoPath" }

Register packages

POST

bower-server:5678/packages

[ { "name": "package-name", "url": "git://repoPath" } ]

Remove package

DELETE

bower-server:5678/packages/<package name>

Remove packages

DELETE

bower-server:5678/packages

["package-name"]

Restart server

POST

bower-server:5678/restart

Refresh caches

POST

bower-server:5678/refresh

Authentication

Authentication can be enabled for the following features:

• Register package
• Register packages
• Remove package
• Remove packages
• Restart server

Add Auth-Key header to request.

Auth-Key = password

Log4js configuration

There are two appenders set in the example configuration. You need to remove one of the two if you want to use it. fileDate appender will write the log to a file which will be rotated daily. Console will write the logging to the console in the log4js format. You need to set the replaceConsole to true if you want to write the logging to the log4j appenders. See github.com/nomiddlename/log4js-node for more information

Tips for usage

Server as a service

• Installing on Ubuntu
• Install as a Windows service

Use behind proxy

git config --global url."https://".insteadOf git://

Calling the API

• do not forget to set the Content-Type header to application/json

Contributing

Please read the rules of contributing on the contribution page.

License

The MIT License (MIT)

Copyright (c) 2014 Hacklone https://github.com/Hacklone

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.