Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use btcNodes argument in regtest mode. #1416

Merged

Conversation

blabno
Copy link

@blabno blabno commented Mar 2, 2018

This is needed for bisq-api and bitcoin docker containers to see each other during dockerized regtest.

@blabno blabno requested a review from ManfredKarrer as a code owner March 2, 2018 21:56
@@ -196,7 +196,7 @@ protected void onSetupCompleted() {
};

if (params == RegTestParams.get()) {
configPeerNodesForRegTest();
configPeerNodesForRegTest(socks5Proxy);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would prefer to have additional checks here and not call configPeerNodes(proxy); from configPeerNodesForRegTest. What is the usecase that you need?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When each node runs in separate docker container they have different IPs and are not reachable by localhost. Regtest mode currently forces to use specific bitcoin node IP or tries to use localhost.
I need ability to point bisq to specific IP in regtest mode.

@ManfredKarrer ManfredKarrer merged commit 961b014 into bisq-network:master Mar 5, 2018
@blabno blabno deleted the feature/allow-btcNodes-in-regtest branch April 6, 2018 09:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants