From 4465aa41347d206c037f16b6003b0ffddd0c831a Mon Sep 17 00:00:00 2001 From: orco Date: Sun, 30 Jun 2019 14:27:33 +0200 Subject: [PATCH] code markdown for commands and paths in README.md ... instead of quotes --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 6a1b28be..5fcf79c1 100644 --- a/README.md +++ b/README.md @@ -23,7 +23,7 @@ Some of the UI tests will fail because they haven't been written yet :-/ ### Running -You need to have an I2P router up and running on the same machine. After you build the application, look inside "gui/build/distributions". Untar/unzip one of the "shadow" files and then run the jar contained inside by typing "java -jar MuWire-x.y.z.jar" in a terminal or command prompt. If you use a custom I2CP host and port, create a file $HOME/.MuWire/i2p.properties and put "i2cp.tcp.host=" and "i2cp.tcp.port=" in there. +You need to have an I2P router up and running on the same machine. After you build the application, look inside `gui/build/distributions`. Untar/unzip one of the `shadow` files and then run the jar contained inside by typing `java -jar MuWire-x.y.z.jar` in a terminal or command prompt. If you use a custom I2CP host and port, create a file `$HOME/.MuWire/i2p.properties` and put `i2cp.tcp.host=` and `i2cp.tcp.port=` in there. The first time you run MuWire it will ask you to select a nickname. This nickname will be displayed with search results, so that others can verify the file was shared by you. It is best to leave MuWire running all the time, just like I2P.