[bisq-network/bisq] Add Makefile for automating localnet setup (#3718)

[Justin Carter]

bodymindarts commented on this pull request.



> +# Deploy a complete localnet by running all required Bitcoin and Bisq
+# nodes, each in their own named screen window. If you are not a screen
+# user, you'll need to run each of the make commands manually in a
+# separate terminal or as a background job.
+#
+# NOTE: You MUST already be attached to a screen session for the
+# following commands to work properly.
+deploy: setup
+	screen -t bitcoin make bitcoind
+	sleep 2    # wait for bitcoind rpc server to start
+	make block # generate a block to ensure Bisq nodes get dao-synced
+	screen -t seednode make seednode
+	screen -t seednode2 make seednode2
+	screen -t alice make alice
+	screen -t bob make bob
+	screen -t mediator make mediator

That makes a lot of sense. I think it should however be the responsibility of the `bitcoind` command to spin it up in a way that is consistent for the other commands to consume.

When adding an alternative `deploy-tmux` command for example that logic has to be duplicated.

Is it still a problem if `block 112` isn't present when the desktop client sping up but appears very soon thereafter?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/bisq/pull/3718#discussion_r352271890
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20191129/439bb3de/attachment.html>