Skip to content

Latest commit

 

History

History
116 lines (76 loc) · 2.43 KB

README.md

File metadata and controls

116 lines (76 loc) · 2.43 KB

BitGreen Web Wallet Backend

This is the BitGreen Web Wallet Backend.

Install bitgreen node and start node

Setup dependencies and download release of bitgreen node

Build doc will be found here:

https://github.com/bitgreen/bitgreen/releases

Run the following commands:

    wget https://github.com/bitgreen/bitgreen/releases/download/v1.3.1/bitgreen-1.3.1-x86_64-linux-gnu.tar.gz
    tar -zxvf bitgreen-1.3.1-x86_64-linux-gnu.tar.gz
    mv bitgreen*/bin/* /usr/local/bin

Node config

Config file can be found here:

    ~/.bitgreen/bitgreen.conf

Config should be following:

    rpcuser=user
    rpcpassword=PASSWORD
    rpcallowip=ALLOWEDIP_RANGE
    listen=1
    server=1
    daemon=1
    logtimestamps=1
    maxconnections=1024

This will use default rpc port 9332.

Start bitgreen node

Start node:

    bitgreend

Check node status:

    bitgreen-cli getinfo

Check rpc provider

curl --data-binary '{"id": 1, "method": "getinfo", "rpc": "1.0"}' http://user:[email protected]:9332/

Run backend service

Setup nodejs. To run backend server, use the following:

    sudo apt-get install build-essential
    npm install
    sudo npm install -g pm2
    pm2 start pm2.json

Run backend in production mode

    pm2 start pm2.json --env production

Run backend in development mode

    pm2 start pm2.json --env development
    or
    pm2 start pm2.json

Then, whenever you need to restart the backend, you can run:

    pm2 restart bitg-wallet-backend

To view more detailed documentation regarding the API, check out the API documentation.

This application integrates the following services & APIs:

Adding DNS or SSL

If you want to add DNS or SSL through Nginx and certbot, you can follow the configuration steps here on ubuntu 18.04+.

Once it is setup, make sure to add a proxy_pass rule instead of serving the files on the filesystem:

location / {
    proxy_pass http://127.0.0.1:8080/;
}

You can use whichever port is defined in the config folder of this application, but by default it runs on port 8080. If SSL is enabled, make sure the rule that you update with a proxy_pass is a secure one.