Skip to content

Latest commit

 

History

History
180 lines (125 loc) · 6.05 KB

build.md

File metadata and controls

180 lines (125 loc) · 6.05 KB
Raw

Building Bisq 2

  1. Clone Bisq 2

    git clone https://github.com/bisq-network/bisq2
cd bisq2

  2. Build Bisq

    On macOS and Linux, execute:

    ./gradlew build

    On Windows:

    gradlew.bat build

    If you prefer to skip tests to speed up the building process, just append -x test to the previous commands.

Important notes

  1. You do not need to install Gradle to build Bisq. The gradlew shell script will install it for you, if necessary.

  2. Bisq requires JDK 17. You can find out which version you have with:

    javac -version

  3. Bisq requires JavaFX to be installed.

  4. Adjustment for IntelliJ IDE (if used) Bisq developers use by default the IntelliJ development IDE (Community edition is free to use). If running from the IDE one need to enable annotation processing (search for that in the settings). The Protocol Buffers plugin need to be installed as well.

Running Bisq

To run the Bisq 2 desktop app with Gradle and the default settings (using the Tor network) use:

./gradlew desktop:desktop-app:run

In that configuration the desktop app connects to the public seed nodes via the Tor network.

The default data directory is: Bisq2

For development, you might want to customize the options and use localhost instead of Tor. In that case you need to run your own seed node as well. Bisq 2 use JVM arguments and has only limited support for program arguments (see below).

How to pass options

JVM arguments

We use the typesafe config framework which expects JVM arguments.

One can pass JVM options in the IntelliJ IDE Run Configuration or add it as JAVA_OPTS to gradle sh installer scripts:

JAVA_OPTS="-Dapplication.appName=bisq2_seed1 \
    -Dapplication.network.configByTransportType.clear.defaultNodePort=8000 \
    -Dapplication.network.supportedTransportTypes.0=CLEAR \
    apps/seed-node-app/build/install/seed-node-app/bin/seed-node-app

Adding JVM options to the binary can be done as follows:

[PATH TO BINARY] -Dapplication.appName=bisq2_Alice_clear \
	    -Dapplication.network.supportedTransportTypes.0=CLEAR

Note, that the Bisq 2 binary has a space in the file name, so you need to use a backslash before the space (Bisq\ 2).

Supported program arguments

Aditionally to the JVM options we support 2 program arguments:

--app-name and --data-dir. Option name and value is seperated with =.

--app-name has the same function as appName in the config.

Program arguments can be added directly to the gradle sh installer scripts:

apps/desktop/desktop-app/build/install/desktop-app/bin/desktop-app --data-dir=<data_dir>

Adding custom config file

A custom config file with the file name bisq.conf can be added to the data directory. If a custom data directory is used it should be provided by a program argument or as JVM argument, otherwise the config file would be expected in the default Bisq2 data directory.

The custom config file overrides the default config files for the entries which are defined in the custom file. The default config file can be found at: https://github.com/bisq-network/bisq2/blob/main/apps/desktop/desktop-app/src/main/resources/desktop.conf

As this file gets frequently updated with new releases, one should only use the entries which one wants to override. The structure from the default config must be maintained.

Example:

Overriding the marketPrice provider with a self-hosted one would be done as follows:

application {
    bondedRoles = {
        marketPrice = {
            providers = [
                        {
                            url = "http://[MY_ONION_ADDRESS].onion"
                            operator = "my own node",
                        }
                    ]
        }
    }
}

Only change entries which are clear to you as inappropriate values could lead to issues.

Run developer setup

Running a development seed node with JVM arguments

First create the gradle installer script for the seed-node-app: ./gradlew :apps:seed-node-app:installDist

Pass the JVM arguments to the installer script:

JAVA_OPTS="-Dapplication.appName=bisq2_seed1 \
    -Dapplication.network.configByTransportType.clear.defaultNodePort=8000 \
    -Dapplication.network.supportedTransportTypes.0=CLEAR \
    -Dapplication.network.seedAddressByTransportType.clear.0=127.0.0.1:8000 \
    -Dapplication.network.seedAddressByTransportType.clear.1=127.0.0.1:8001" \
    apps/seed-node-app/build/install/seed-node-app/bin/seed-node-app

Optionally you can run a second seed node at port 8001:

JAVA_OPTS="-Dapplication.appName=bisq2_seed1 \
    -Dapplication.network.configByTransportType.clear.defaultNodePort=8001 \
    -Dapplication.network.supportedTransportTypes.0=CLEAR \
    -Dapplication.network.seedAddressByTransportType.clear.0=127.0.0.1:8000 \
    -Dapplication.network.seedAddressByTransportType.clear.1=127.0.0.1:8001" \
    apps/seed-node-app/build/install/seed-node-app/bin/seed-node-app

Running a development desktop application with JVM arguments:

First create the gradle installer script for the desktop-app: ./gradlew :desktop:desktop-app:installDist

Pass the JVM arguments to the installer script:

JAVA_OPTS="-Dapplication.appName=bisq2_Alice_clear \
    -Dapplication.network.supportedTransportTypes.0=CLEAR \
    -Dapplication.network.seedAddressByTransportType.clear.0=127.0.0.1:8000 \
    -Dapplication.network.seedAddressByTransportType.clear.1=127.0.0.1:8001" \
    apps/desktop/desktop-app/build/install/desktop-app/bin/desktop-app

Optionally you can pass that data directory as program argument as follows: apps/desktop/desktop-app/build/install/desktop-app/bin/desktop-app --data-dir=bisq2_Alice_clear

You likely want to run a second desktop application for testing the trade use case with 2 traders (e.g. Alice and Bob). Just change the -Dapplication.appName to something like bisq2_Bob_clear in the above configuration.