Marty Jones
Marty Jones
Below is how I was able to include environment variables without needing to commit them to source (assumes you're using GitHub actions to deploy your app). **Tradeoffs of this approach:**...
> @murtyjones Your comment "figuring out how to get AWS Secret Manager working, that would probably be a better workaround," -- Makes me believe I am pushing into a rope...
Should've read the comments. Makes sense! Thank you
> For now, to sync the UI with the state of the nodes, first click on the canvas, then click on the Sync icon at the top of the sidebar....
> We need to implement subscriptions to the `lnd` streaming RPCs I've started to play around with this but dealing with an issue that I'm not familiar enough with Electron/this...
Okay, I think that makes sense! I'll play around with the implementations' support for event streaming and see what I find
Spent a little bit of time with this [here](https://github.com/murtyjones/lightning-listening/blob/master/src/index.ts) and discovered the following: - `lnd` has streaming as discussed - `eclair` exposes a [websocket](https://acinq.github.io/eclair/#websocket) with channel opening events - `c-lightning`...
@xgz123 mind sharing the code you used to the change the source?
Since this issue is pretty old at this point I figured I'd ask a followup: Is there an idiomatic way to access a node's siblings?
Seems like what's on `master` needs to be published to npm. This is what version 1.1.0 (latest release) looks like locally