This is the official repo for the bPanel project, a full featured, enterprise level GUI for your bcoin Bitcoin node.

For complete developer and API documentation, visit our website: https://bpanel.org

• npm >= 5.7.1
• node >= 8.9.4

NOTE: It is important to be using at least this version of npm because of a bug that removes node_modules that are installed from GitHub and doesn't reinstall them which breaks the build

If you already have a bcoin node running that you would like to use bPanel to interact with, add the relevant configurations (uri, api-key, network etc.) to a configuration file ~/.bpanel/clients/default.conf and run:

npm install
npm start

You can save as many confs for as many compatible nodes as you want and use the argument client-id to connect to them. For example, save another set of configurations to a file ~/.bpanel/clients/main.conf and run:

npm start -- --client-id=main

Configurations can also be passed via the command line or environment variables prefaced with BPANEL_. Read more about configuring bPanel here.

From inside the project directory in your terminal, run:

npm install && docker-compose up -d

This will start up three docker services as background daemon processes. Once everything has started up, you should be able to see your bPanel instance at localhost:5000.

Read more about using Docker with bPanel below.

The default configs in the standard docker-compose.yml file bring up multiple containers

• bcoin bitcoin node/wallet (running a regtest node)
• bPanel routing + static file server (connecting to the regtest node)
• TLS terminating reverse proxy

Some plugins require TLS to function properly (such as hardware signing support).

(To learn how to use bpanel for existing bcoin nodes on any network, read about configuring bPanel below).

The following will generally just be used for quick start, testing, and development purposes (though it could be used in production with some modification).

To spin up a webapp, reverse-proxy, server, a bcoin node on regtest and a wallet server with multisig support, clone this repo and from the cloned directory do the following:

1. Run npm install to install dependencies and generate necessary constants.
2. Run docker-compose up -d to start everything.
3. Navigate to localhost:5000 to see your webapp.
4. Or navigate to https://localhost to use TLS - you will have to choose to trust the certificate

Requests to the /bcoin will get forwarded to your bcoin node. Requests to the /bwallet endpoint will get forwarded to the wallet server

For local development, you run just the bcoin docker container (docker-compose up -d bcoin) and then npm run start:dev -- --client-id=_docker (or npm run start:poll -- --client-id=_docker for Mac since webpack's watch can behave strangely on macOS) to run bPanel and its server from your local box.

Note that the --client-id argument tells bPanel which client config you want to use. _docker is the name of the config created by the bcoin service.

bPanel comes pre-installed with a default theme called Genesis Theme, that bundles together a set of useful starter plugins and a custom skin called bMenace. If you want, you can disable the Genesis Theme by removing it from the list in pluginsConfig.js, but if you want to keep using some of the plugins from the theme, feel free to add them individually to your config!

To install plugins, simply add the name as a string to the plugins array in webapp/plugins/pluginsConfig.js. Make sure to match the name to the package name on npm (localPlugins can be used for plugins you are developing in the plugins/local directory). Once you save the file, bPanel will automatically install the plugins and rebuild.

Note that if you have some plugins or themes being loaded, this can take around 30 seconds as npm install is run for you.

Discover all the plugins available by running npm search bpanel in your console.

bPanel can be configured to connect to any bcoin-API compatible node you want to point it to, not just the docker container created by the default docker-compose.yml configurations.

Since bPanel just uses bclient to connect to and query nodes, all you need to do is pass the appropriate congifurations when starting up bPanel. This can be done via the command line, environment variables (prefaced with BPANEL_), or through a configuration file. Under the hood, bPanel uses the bcfg module to accomplish this. Learn more about bcfg here.

bPanel looks for configuration files in your home directory in a .bpanel folder (~/.bpanel). This can be changed by passing a prefix argument at runtime. Client configurations for connecting to different nodes are loaded from the clients directory, ~/.bpanel/clients/[CLIENT-ID].conf.

You can have as many different configurations as you want. bPanel will default to a default.conf configuration. To use different configurations, just pass in a client-id argument at runtime. e.g. npm start -- --client-id=test (or as an env variable BPANEL_CLIENT_ID=test) which will load configs from ~/.bpanel/clients/test.conf.

The clients directory can also be customized with the clients-dir argument.

Sample conf files for the client can be found here

Since node and wallet services are run on different servers, you will likely need different configurations to connect to the wallet. These should be in the same client conf file, prefaced with wallet- (note that bcoin looks for these in separate config files). See the sample conf file for an example.

To directly serve bpanel over https without the reverse proxy, set the environment variables:

BPANEL_HTTPS=true
BPANEL_TLS_KEY=<path to key>
BPANEL_TLS_CERT=<path to cert>

There are three docker services in the compose file: bpanel, bcoin and securityc. The bpanel service is an http server that acts as a static file server and as a request router to backend services as well as a webpack process for building your js files. The bcoin service is an instance of bcoin that supports an http server, a wallet server and a bitcoin p2p server.

The securityc service generates TLS keys and certs and runs a TLS terminating reverse proxy. You can use custom configs to connect to an existing node, or use the bcoin docker service to spin up a bcoin node that the webapp will connect to.

These instructions are for if you want to run bPanel within the bpanel service and have it talk to a bcoin node running in a container from the bcoin service. For example, this is how bPanel works out of the box if you simply run docker-compose up -d.

Configurations are shared between the two docker containers using a shared docker volume called configs. Settings for the bcoin nodes in docker are set using environment variables, either in docker-compose.yml or an env file (by default in /etc/bcoin.env but you can point to whichever and as many env files as you want using the env_file configuration in the bcoin service). The bcoin node is started with the bcoin-init.js script. During this process, api keys are generated and all required configurations are saved in a config file called _docker.conf in the shared volume.

If the configs volume is mounted to your host machine, you can connect a local version of bPanel to it by pointing the client-id config at _docker and it will use the appropriate configs.

If you are mounting a local bcoin data dir (~/.bcoin) or persisting using docker volumes, you can also pass settings to your bcoin docker container with a bcoin.conf file (read more about bcoin configurations here).

(This section is only relevant if you will be running a bcoin node in a docker container using the bcoin service, or using the bcoin-init.js script to start a node.)

This setup supports setup scripts for your bcoin node. This will allow you to run scripts on your node for a repeatable and predictable environment for testing or development.

Three circumstances need to be met to run a script:

1. There needs to be a js file to run in the scripts directory that exports a function
2. You need to pass the name of this file (including the extension) as an environment variable named BCOIN_INIT_SCRIPT in the docker-compose or as a init-script setting in your bcoin.conf file
3. There should be no walletdb in the container. This last requirement makes sure that a setup script doesn't overwrite your data if you're mapping volumes or if you restart a container.

These checks are done in bcoin-init.js which is run by the bpanel/bcoin image that is used to create the bcoin container and sets up a node based on the configs described above. Setup scripts are passed the bcoin node object that has been created so the scripts have access to the node being started at run time as well as the relevant configs.

Example setup scripts can be found in the /scripts directory (funded-dummy-wallets.js and setup-coinbase-address.js).

By default, the bcoin and wallet DBs persist in ~/.bcoin. If you want docker to start bcoin with a fresh DB, comment out the bcoin volume in docker-compose.yml then run docker-compose up -d. Alternatively, you can also persist your bcoin data within the named bcoin volume or on the host machine.

Uncomment the relevant build: sections in docker-compose.yml for the services you want to build, then run docker-compose build

The bPanel UI is built entirely around plugins. All visual elements can be extended or overridden via the plugin system including the header, footer, sidebar, and main panel/view element. To get started making your own plugin, use the bPanel-cli

The simplest thing to do, is to create your own server file that includes server/index.js.

const bpanel = require('bpanel')({
  network: 'main', // Put bPanel configs here (optional)
});
const app = require('express')();
app.use( /* Put your own middleware here */ );
app.use( bpanel.app );
app.listen( 5000 );

• Copyright (c) 2018, The bPanel Devs (MIT License).