Skip to content
Snippets Groups Projects
Commit 99d2b419 authored by Éloïs's avatar Éloïs
Browse files

v0.4.0

parent 14ee9635
No related branches found
No related tags found
No related merge requests found
...@@ -35,8 +35,8 @@ ...@@ -35,8 +35,8 @@
- [build-for-arm](./docs/user/build-for-arm.md) - [build-for-arm](./docs/user/build-for-arm.md)
- [rpc](./docs/user/rpc.md) deploy a permanent ǦDev mirror node - [rpc](./docs/user/rpc.md) deploy a permanent ǦDev mirror node
- [smith](./docs/user/smith.md) deploy a permanent ǦDev validator node - [smith](./docs/user/smith.md) deploy a permanent ǦDev validator node
- [end2end-tests](./end2end-tests/) automated end to end tests written with cucumber - [end2end-tests](./end2end-tests/) automated end to end tests written with cucumber
- [live-tests](./live-tests/) sanity checks to test the storage of a live chain - [live-tests](./live-tests/) sanity checks to test the storage of a live chain
## Use ## Use
...@@ -47,7 +47,7 @@ The easiest way is to use the docker image. ...@@ -47,7 +47,7 @@ The easiest way is to use the docker image.
Minimal command to deploy a **temporary** mirror peer: Minimal command to deploy a **temporary** mirror peer:
```docker ```docker
docker run -it -p9944:9944 -e DUNITER_CHAIN_NAME=gdev duniter/duniter-v2s:v0.3.0 --tmp --execution=Wasm docker run -it -p9944:9944 -e DUNITER_CHAIN_NAME=gdev duniter/duniter-v2s:v0.4.0 --tmp --execution=Wasm
``` ```
To go further, read [How to deploy a permanent mirror node on ĞDev network](./docs/user/rpc.md). To go further, read [How to deploy a permanent mirror node on ĞDev network](./docs/user/rpc.md).
...@@ -58,7 +58,7 @@ It can be useful to deploy your local blockchain, for instance to have a control ...@@ -58,7 +58,7 @@ It can be useful to deploy your local blockchain, for instance to have a control
to develop/test an application that interacts with the blockchain. to develop/test an application that interacts with the blockchain.
```docker ```docker
docker run -it -p9944:9944 duniter/duniter-v2s:v0.3.0 --tmp docker run -it -p9944:9944 duniter/duniter-v2s:v0.4.0 --tmp
``` ```
Or use the `docker-compose.yml` at the root of this repository. Or use the `docker-compose.yml` at the root of this repository.
...@@ -69,8 +69,8 @@ By default, your local blockchain produces a new block every 6 seconds, which is ...@@ -69,8 +69,8 @@ By default, your local blockchain produces a new block every 6 seconds, which is
You can decide when to produce blocks with the cli option `--sealing` which has two modes: You can decide when to produce blocks with the cli option `--sealing` which has two modes:
* `--sealing=instant`: produce a block immediately upon receiving a transaction into the transaction pool - `--sealing=instant`: produce a block immediately upon receiving a transaction into the transaction pool
* `--sealing=manual`: produce a block upon receiving an RPC request (method `engine_createBlock`). - `--sealing=manual`: produce a block upon receiving an RPC request (method `engine_createBlock`).
### Autocompletion ### Autocompletion
......
...@@ -7,7 +7,7 @@ services: ...@@ -7,7 +7,7 @@ services:
duniter-v2s: duniter-v2s:
container_name: duniter-v2s container_name: duniter-v2s
# choose the version of the image here # choose the version of the image here
image: duniter/duniter-v2s:v0.3.0 image: duniter/duniter-v2s:v0.4.0
ports: ports:
# telemetry # telemetry
- 9615:9615 - 9615:9615
......
...@@ -9,15 +9,14 @@ ...@@ -9,15 +9,14 @@
# The peer id has to be replaced withe the output of the following command # The peer id has to be replaced withe the output of the following command
# #
# >>> PEER_ID >>> # >>> PEER_ID >>>
# docker run --rm -it --entrypoint duniter -v $PWD:/var/lib/duniter/ duniter/duniter-v2s:v0.3.0 key generate-node-key --file /var/lib/duniter/node.key # docker run --rm -it --entrypoint duniter -v $PWD:/var/lib/duniter/ duniter/duniter-v2s:v0.4.0 key generate-node-key --file /var/lib/duniter/node.key
# <<<<<<<<<<<<<<< # <<<<<<<<<<<<<<<
version: "3.4" version: "3.4"
services: services:
duniter-rpc: duniter-rpc:
image: duniter/duniter-v2s:v0.3.0 image: duniter/duniter-v2s:v0.4.0
restart: unless-stopped restart: unless-stopped
ports: ports:
# telemetry # telemetry
......
...@@ -2,7 +2,7 @@ version: "3.4" ...@@ -2,7 +2,7 @@ version: "3.4"
services: services:
duniter-rpc: duniter-rpc:
image: duniter/duniter-v2s:v0.3.0 image: duniter/duniter-v2s:v0.4.0
restart: unless-stopped restart: unless-stopped
ports: ports:
# telemetry # telemetry
...@@ -24,12 +24,12 @@ services: ...@@ -24,12 +24,12 @@ services:
# SERVER_DOMAIN should be replaced by a domain name that point on your server # SERVER_DOMAIN should be replaced by a domain name that point on your server
# #
# The PEER_ID should be replaced by the output of this command: # The PEER_ID should be replaced by the output of this command:
# docker run --rm -it --entrypoint -v $PWD/duniter-rpc/:/var/lib/duniter/ duniter duniter/duniter-v2s:v0.3.0 key generate-node-key --file /var/lib/duniter/node.key # docker run --rm -it --entrypoint -v $PWD/duniter-rpc/:/var/lib/duniter/ duniter duniter/duniter-v2s:v0.4.0 key generate-node-key --file /var/lib/duniter/node.key
- "/dns/${SERVER_DOMAIN?SERVER_DOMAIN should be set}/tcp/30333/p2p/${PEER_ID?PEER_ID should be set}" - "/dns/${SERVER_DOMAIN?SERVER_DOMAIN should be set}/tcp/30333/p2p/${PEER_ID?PEER_ID should be set}"
- "--rpc-cors=all" - "--rpc-cors=all"
duniter-validator: duniter-validator:
image: duniter/duniter-v2s:v0.3.0 image: duniter/duniter-v2s:v0.4.0
restart: unless-stopped restart: unless-stopped
ports: ports:
# telemetry # telemetry
...@@ -52,7 +52,7 @@ services: ...@@ -52,7 +52,7 @@ services:
# SERVER_DOMAIN should be replaced by a domain name that point on your server # SERVER_DOMAIN should be replaced by a domain name that point on your server
# #
# The VALIDATOR_PEER_ID should be replaced by the output of this command: # The VALIDATOR_PEER_ID should be replaced by the output of this command:
# docker run --rm -it --entrypoint -v $PWD/duniter-rpc/:/var/lib/duniter/ duniter duniter/duniter-v2s:v0.3.0 key generate-node-key --file /var/lib/duniter/node.key # docker run --rm -it --entrypoint -v $PWD/duniter-rpc/:/var/lib/duniter/ duniter duniter/duniter-v2s:v0.4.0 key generate-node-key --file /var/lib/duniter/node.key
- "/dns/${SERVER_DOMAIN?SERVER_DOMAIN should be set}/tcp/30333/p2p/${VALIDATOR_PEER_ID?VALIDATOR_PEER_ID should be set}" - "/dns/${SERVER_DOMAIN?SERVER_DOMAIN should be set}/tcp/30333/p2p/${VALIDATOR_PEER_ID?VALIDATOR_PEER_ID should be set}"
- "--rpc-cors=all" - "--rpc-cors=all"
- "--rpc-methods=Unsafe" - "--rpc-methods=Unsafe"
......
...@@ -5,18 +5,21 @@ ...@@ -5,18 +5,21 @@
### Duniter part ### Duniter part
- Add this docker-compose template on your server: - Add this docker-compose template on your server:
[docker/compose/gdev-rpc.docker-compose.yml](https://git.duniter.org/nodes/rust/duniter-v2s/-/blob/master/docker/compose/gdev-mirror.docker-compose.yml) [docker/compose/gdev-rpc.docker-compose.yml](https://git.duniter.org/nodes/rust/duniter-v2s/-/blob/master/docker/compose/gdev-mirror.docker-compose.yml)
- Rename the file : `mv gdev-mirror.docker-compose.yml docker-compose.yml` - Rename the file : `mv gdev-mirror.docker-compose.yml docker-compose.yml`
- In the same folder, create a `.env` file that defime environment variables `SERVER_DOMAIN` and `PEER_ID`: - In the same folder, create a `.env` file that defime environment variables `SERVER_DOMAIN` and `PEER_ID`:
```bash ```bash
SERVER_DOMAIN=YOUR_DOMAIN SERVER_DOMAIN=YOUR_DOMAIN
PEER_ID=YOUR_PEER_ID PEER_ID=YOUR_PEER_ID
``` ```
Your `PEER_ID` shoud be generated with this command: Your `PEER_ID` shoud be generated with this command:
```bash ```bash
docker run --rm -it --entrypoint duniter -v $PWD:/var/lib/duniter/ duniter/duniter-v2s:v0.3.0 key generate-node-key --file /var/lib/duniter/node.key docker run --rm -it --entrypoint duniter -v $PWD:/var/lib/duniter/ duniter/duniter-v2s:v0.4.0 key generate-node-key --file /var/lib/duniter/node.key
``` ```
- If you have write access errors run in docker-compose.yml folder : `chmod o+rwX -R .` - If you have write access errors run in docker-compose.yml folder : `chmod o+rwX -R .`
- Do `docker compose up -d` to start your node - Do `docker compose up -d` to start your node
...@@ -63,6 +66,7 @@ server { ...@@ -63,6 +66,7 @@ server {
} }
} }
``` ```
and replace `YOUR_DOMAIN` by your domain each time. and replace `YOUR_DOMAIN` by your domain each time.
- [generate your ssl certificates](https://github.com/acmesh-official/acme.sh) with let's encrypt - [generate your ssl certificates](https://github.com/acmesh-official/acme.sh) with let's encrypt
......
...@@ -5,12 +5,12 @@ ...@@ -5,12 +5,12 @@
### Duniter part ### Duniter part
- Add this docker-compose on your server : - Add this docker-compose on your server :
[docker/compose/gdev-validator.docker-compose.yml](https://git.duniter.org/nodes/rust/duniter-v2s/-/blob/master/docker/compose/gdev-validator.docker-compose.yml) [docker/compose/gdev-validator.docker-compose.yml](https://git.duniter.org/nodes/rust/duniter-v2s/-/blob/master/docker/compose/gdev-validator.docker-compose.yml)
- Create a `.env` file that define environment variables `SERVER_DOMAIN`, `PEER_ID` and `VALIDATOR_PEER_ID`: - Create a `.env` file that define environment variables `SERVER_DOMAIN`, `PEER_ID` and `VALIDATOR_PEER_ID`:
- `SERVER_DOMAIN`: a domain name that point on your server - `SERVER_DOMAIN`: a domain name that point on your server
- `PEER_ID`: Your rpc node peer id, shoud be generated with this command: `docker run --rm -it --entrypoint -v $PWD:/var/lib/duniter/ duniter duniter/duniter-v2s:v0.3.0 key generate-node-key --file /var/lib/duniter/rpc-node.key` - `PEER_ID`: Your rpc node peer id, shoud be generated with this command: `docker run --rm -it --entrypoint -v $PWD:/var/lib/duniter/ duniter duniter/duniter-v2s:v0.4.0 key generate-node-key --file /var/lib/duniter/rpc-node.key`
- `VALIDATOR_PEER_ID`: Your validator node peer id, shoud be generated with this command: `docker run --rm -it --entrypoint duniter -v $PWD:/var/lib/duniter/ duniter/duniter-v2s:v0.3.0 key generate-node-key --file /var/lib/duniter/validator-node.key` - `VALIDATOR_PEER_ID`: Your validator node peer id, shoud be generated with this command: `docker run --rm -it --entrypoint duniter -v $PWD:/var/lib/duniter/ duniter/duniter-v2s:v0.4.0 key generate-node-key --file /var/lib/duniter/validator-node.key`
Note: duniter-rpc PEER_ID and duniter-validator PEER_ID isn't the same. Note: duniter-rpc PEER_ID and duniter-validator PEER_ID isn't the same.
- If you have write access errors run in docker-compose.yml folder : `chmod o+rwX -R .` - If you have write access errors run in docker-compose.yml folder : `chmod o+rwX -R .`
- `docker compose up -d` to start your node - `docker compose up -d` to start your node
...@@ -57,6 +57,7 @@ server { ...@@ -57,6 +57,7 @@ server {
} }
} }
``` ```
and replace `YOUR_DOMAIN` by your domain each time. and replace `YOUR_DOMAIN` by your domain each time.
- [generate your ssl certificates](https://github.com/acmesh-official/acme.sh) with let's encrypt - [generate your ssl certificates](https://github.com/acmesh-official/acme.sh) with let's encrypt
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment