interledgerjs / moneyd-gui

Graphical interface for moneyd

Moneyd GUI

A GUI for Moneyd

• Usage
• Environment Variables
• TODOs
• More Screenshots

Usage

git clone [email protected]:interledgerjs/moneyd-gui.git
cd moneyd-gui
npm install
npm start

Make sure you start Moneyd with --admin-api-port 7769.

Then go to localhost:7770 in your browser.

Environment Variables

Variable	Default	Purpose
PORT	7770	Port to host the GUI's webserver on
ADMIN_API_PORT	7769	Port for moneyd's admin API. Set with --admin-api-port in moneyd

TODOs

• CORS
• live update on receiver page
• live update on balances
• spiffier transitions?
• better 404 page
• better 500 page (instruct to turn on moneyd with flag)
• health check for moneyd by using plugin btp?
• ping tool
• network indicator
• send tool
• receive tool
• implement statistics
• align icons and labels properly
• highlight selected item in nav
• make exchange rates more of a grid
• some visualizations?
• links to tutorials
• web monetization health

More Screenshots

Send SPSP Payments

View Routing Table Info

Receive SPSP Payments

Network Graph

The network graph is a visualization of your node's routing table. It doesn't represent a complete view of the network.

moneyd-gui's Issues

Moneyd GUI should listen on localhost only!

Moneyd GUI provides access to your moneyd and currently listens on all interfaces. So if you're running this GUI, anyone on your network can help themselves to all of your money. Not great.

At a minimum, moneyd GUI should default to localhost only.

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

Feature Request: Add Plugin Version Number Column to Plugin Info Page

Ease of administration feature request. A more robust version of this Feature Request would possibly check Github or NPM repositories to see if plugin versions are at a level equal to current release version, and if not, indicate within the Plugin Info page both the current version, and the latest version available. Realize this may not be desired as an automated function due to concerns about unneeded or out of scope communication to outside resources/repositories - which in the event that is a concern - possibly place a button on the page that would serve as an authorization of version checking from the appropriate repositories.

Feature Request: Allow Click/Drilldown of ILSP Node in Network Graph to View an ILSP's Peers/Info/Admin

Modify the Network Graph capabilities to allow for selecting an ILSP in the graph to "drilldown" to the ILSPs current peering relationships. This information could be gleaned from a collection of a peer's routing updates.

Future function could also provide a subset of the peer's information to be displayed - such as exchange rates, network latency, balances, loads, uptimes, etc.

Could serve as an alternative method for ILSP Operators to select a peer and perform certain functions for administration or perhaps merely presenting a button that would take you to that peer's administrative functions / settings.

ilp-ws-reconnect debug websocket disconnected with Error: connect ECONNREFUSED 127.0.0.1:7768; reconnect in 5000

I have made sure that the port is open. Full stack:

2018-05-08T11:20:40.821Z ilp-ws-reconnect debug websocket disconnected with Error: connect ECONNREFUSED 127.0.0.1:7768; reconnect in 5000
(node:16333) UnhandledPromiseRejectionWarning: Error: connection aborted
    at AbstractBtpPlugin.once (/Users/paulrberg/Documents/projects/clones/moneyd-gui/node_modules/ilp-plugin-btp/index.js:215:21)
    at Object.onceWrapper (events.js:254:19)
    at AbstractBtpPlugin.emit (events.js:159:13)
    at AbstractBtpPlugin._emitDisconnect (/Users/paulrberg/Documents/projects/clones/moneyd-gui/node_modules/ilp-plugin-btp/index.js:472:12)
    at WebSocketReconnector._ws.on (/Users/paulrberg/Documents/projects/clones/moneyd-gui/node_modules/ilp-plugin-btp/index.js:200:39)
    at WebSocketReconnector.EventEmitter.emit (/Users/paulrberg/Documents/projects/clones/moneyd-gui/node_modules/eventemitter2/lib/eventemitter2.js:351:19)
    at WebSocketReconnector._reconnect (/Users/paulrberg/Documents/projects/clones/moneyd-gui/node_modules/ilp-plugin-btp/ws-reconnect.js:33:10)
    at WebSocket._instance.on (/Users/paulrberg/Documents/projects/clones/moneyd-gui/node_modules/ilp-plugin-btp/ws-reconnect.js:17:46)
    at WebSocket.emit (events.js:159:13)
    at WebSocket.finalize (/Users/paulrberg/Documents/projects/clones/moneyd-gui/node_modules/ilp-plugin-btp/node_modules/ws/lib/WebSocket.js:182:41)
    at ClientRequest._req.on (/Users/paulrberg/Documents/projects/clones/moneyd-gui/node_modules/ilp-plugin-btp/node_modules/ws/lib/WebSocket.js:647:10)
    at ClientRequest.emit (events.js:159:13)
    at Socket.socketErrorListener (_http_client.js:389:9)
    at Socket.emit (events.js:159:13)
    at emitErrorNT (internal/streams/destroy.js:64:8)
    at process._tickCallback (internal/process/next_tick.js:152:19)
(node:16333) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:16333) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Print something when it's running

So it's obvious that it worked