-
Install Rust and rustup (https://www.rust-lang.org/install.html).
-
Install required native libraries and utilities:
apt-get update && \ apt-get install -y \ build-essential \ pkg-config \ cmake \ libssl-dev \ libsqlite3-dev \ libzmq3-dev \ libncursesw5-dev
-
libindy
requires the modern1.0.14
version oflibsodium
but Ubuntu 16.04 does not support installation it's fromapt
repository. Because of this, it requires to build and installlibsodium
from source:
cd /tmp && \
curl https://download.libsodium.org/libsodium/releases/libsodium-1.0.14.tar.gz | tar -xz && \
cd /tmp/libsodium-1.0.14 && \
./configure --disable-shared && \
make && \
make install && \
rm -rf /tmp/libsodium-1.0.14
-
Build
libindy
git clone https://github.com/hyperledger/indy-sdk.git cd ./indy-sdk/libindy cargo build cd ..
Note: libindy
debian package, installed from the apt repository, is statically linked with libsodium
.
For manually building this can be achieved by passing --features sodium_static
into cargo build
command.
-
Run integration tests:
-
Start local nodes pool on
127.0.0.1:9701-9708
with Docker:docker build -f ci/indy-pool.dockerfile -t indy_pool . docker run -itd -p 9701-9708:9701-9708 indy_pool
In some environments, this approach with mapping of local ports to container ports can't be applied. Dockerfile
ci/indy-pool.dockerfile
supports optional pool_ip param that allows changing ip of pool nodes in generated pool configuration. The following commands allow to start local nodes pool in custom docker network and access this pool by custom ip in docker network:docker network create --subnet 10.0.0.0/8 indy_pool_network docker build --build-arg pool_ip=10.0.0.2 -f ci/indy-pool.dockerfile -t indy_pool . docker run -d --ip="10.0.0.2" --net=indy_pool_network indy_pool
If you use this method then you have to specify the TEST_POOL_IP as specified below when running the tests.
It can be useful if we want to launch integration tests inside another container attached to the same docker network.
-
Run tests
cd libindy RUST_TEST_THREADS=1 cargo test
It is possible to change ip of test pool by providing of TEST_POOL_IP environment variable:
RUST_TEST_THREADS=1 TEST_POOL_IP=10.0.0.2 cargo test
-
-
Build
indy-cli
(Optional)indy-cli
is dependent onlibindy
and should be built after it.cd cli/ RUSTFLAGS=" -L ../libindy/target/debug" cargo build
If you have followed the instructions to build libindy above, the default build type will be
debug
Make sure to add the libindy to the path. Using bash:
echo "export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/path/to/libindy/target/{BUILD TYPE}" >> ~/.bashrc sudo ldconfig source ~/.bashrc
To run indy-cli, navigate to
cli/target/debug
and run./indy-cli
See libindy/ci/ubuntu.dockerfile for example of Ubuntu based environment creation in Docker.