You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now bet is communicating with c-lightning and chips via CLI commands.
This must be updated to instead use RPC communication, so that bet does not rely on command line path settings etc and be working independently. RPC specific issue can be tracked here: #179
For "bet" specific data directory based on different platforms, I'd suggest to make a data directory for bet specific configuration files. Like for different OS, it should be like:
And under this bet's data directory we can move files located from privatebet/config/ directory:
cashier_nodes.json
dealer_config.json
There we can also have the chipsbet.conf file created to get the RPC information for both c-lightning and Chips. Example:
CHIPS_RPC_IP=127.0.0.1
CHIPS_RPC_PORT=57776
CHIPS_RPC_USER=chip_rpc_username
CHIPS_RPC_PASSWORD=chips_rpc_password
# c-lightning only provides JSON-RPC socket, and no HTTP RPC API
CHIPS_C_LIGHTNING_RPC_SOCKET=/home/username/.chipsln/chips/chipsln-rpc
The text was updated successfully, but these errors were encountered:
satindergrewal
changed the title
Replace third party applications communication via APIs instead of CLI commands
Using system specific data directory for "bet" for reading cashier/dealer and RPC API config info
Jun 23, 2021
satindergrewal
changed the title
Using system specific data directory for "bet" for reading cashier/dealer and RPC API config info
Data directory for "bet" for reading cashier/dealer and RPC API config info
Jun 23, 2021
Right now
bet
is communicating withc-lightning
andchips
via CLI commands.This must be updated to instead use RPC communication, so that
bet
does not rely on command line path settings etc and be working independently. RPC specific issue can be tracked here: #179For "bet" specific data directory based on different platforms, I'd suggest to make a data directory for
bet
specific configuration files. Like for different OS, it should be like:$HOME/.chipsbet/
$HOME/Library/Applications Support/Chipsbet/
%AppData%\Chipsbet
And under this
bet
's data directory we can move files located fromprivatebet/config/
directory:There we can also have the
chipsbet.conf
file created to get the RPC information for bothc-lightning
andChips
. Example:CHIPS_RPC_IP=127.0.0.1 CHIPS_RPC_PORT=57776 CHIPS_RPC_USER=chip_rpc_username CHIPS_RPC_PASSWORD=chips_rpc_password # c-lightning only provides JSON-RPC socket, and no HTTP RPC API CHIPS_C_LIGHTNING_RPC_SOCKET=/home/username/.chipsln/chips/chipsln-rpc
The text was updated successfully, but these errors were encountered: