Jamal James

Thanks for the sneak peak @amovfx. I don't think this value needs to be changed multiple times. My suggestion would be to only allow setting this option when the network...

I just re-read the initial request and my response. AFAICT the goal is to have Polar use a docker network that has already been pre-created by the user. So they...

@amovfx Thanks for the update. Can you open a PR so we can discuss the changes there?

Hey @NonsoAmadi10 thanks for offering to assist with this. For Eclair, Polar currently uses the files in the [docker/eclair](https://github.com/jamaljsr/polar/tree/master/docker/eclair) dir to build the image. The README in the [docker](https://github.com/jamaljsr/polar/tree/master/docker) dir...

Yes, I'd appreciate the contribution if you'd like to help. > Also I would love to know how I can contribute, do I check into your branch after forking and...

@Abdulkbk yes, Polar will already detect and avoid using ports that are already in use. The situation that @dangeross is describing is that initially Polar assigns LND REST ports starting...

Hey @umarluqman, thanks for taking a shot at this feature. The data in the store that you found are actually all derived from the node names in the network object....

Go for it 👍

Hey @Jem256, yes you will have to implement an function in the designer store to rename the node in it's state as well. Take a look at how `removeLightningNode` is...

Hey @Jem256, can you push the code that exhibits this behavior so I can reproduce it and investigate.