Please see commits for review/changes.
This PR contains the following breaking changes:
* The BTCPay configuration has all been moved to env vars/settings
* The LndHub admin token has been moved from the credentials file to an env var/setting
* The public API for BTCPay balances has been renamed from "api/kredits" to "api/btcpay"
* The amounts of the onchain balances are now sats instead of BTC
refs #31
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Please see commits for review/changes.
This PR contains the following breaking changes:
refs #31
utACK.
@@ -41,0 +46,4 @@default: ENV["BTCPAY_API_URL"].presencefield :btcpay_enabled, type: :boolean,default: (ENV["BTCPAY_API_URL"].present?.to_s || false)the default is here either a string or a boolean? can it handle both?
This just got copypasta'd across the whole file, for some reason that I'm sure is now forgottten. I have removed the silliness just now.
@@ -0,0 +5,4 @@def initialize@base_url = Setting.btcpay_api_url@store_id = Setting.btcpay_store_id@auth_token = Setting.btcpay_auth_tokenI'd use attr_readers here then it is a bit clearer that those are also potentially used from the outside/from inheriting classes
@@ -55,3 +55,3 @@namespace :api doget 'kredits/onchain_btc_balance', to: 'kredits#onchain_btc_balance'get 'btcpay/onchain_btc_balance', to: 'btcpay#onchain_btc_balance'where do we use those again?
https://kredits.kosmos.org/budget
@@ -0,0 +1,22 @@## API Docs: https://docs.btcpayserver.org/API/Greenfield/v1/#class BtcpayManagerService < LdapServiceOops.
@bumi Thanks! Addressed all comments.
@bumi Can you review the latest changes and approve the PR if they're good to go?
LGTM