From 90b01eaa81816d3638a34fe1d39e7f8367cb78c5 Mon Sep 17 00:00:00 2001 From: vincentux <vincentux@vincentux.fr> Date: Wed, 8 Jun 2022 20:26:18 +0200 Subject: [PATCH] =?UTF-8?q?Plusieurs=20petits=20correctifs=20Par=20contre?= =?UTF-8?q?=20je=20n'est=20pas=20test=C3=A9=20l'option=20-f=20de=20docker-?= =?UTF-8?q?compose?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- docs/user/rpc.md | 18 +++++++++++------- 1 file changed, 11 insertions(+), 7 deletions(-) diff --git a/docs/user/rpc.md b/docs/user/rpc.md index 80af18217..c160c3223 100644 --- a/docs/user/rpc.md +++ b/docs/user/rpc.md @@ -6,11 +6,15 @@ - Add this docker-compose on your server : [docker/compose/gdev-rpc.docker-compose.yml](https://git.duniter.org/nodes/rust/duniter-v2s/-/blob/master/docker/compose/gdev-rpc.docker-compose.yml) -- Create a `.env` file that defime environment variables `SERVER_DOMAIN` and `PEER_ID`: - - `SERVER_DOMAIN`:Â a domain name that point on your server - - `PEER_ID`: Your node peer id, shoud be generated with this command:Â `docker run --rm -it --entrypoint duniter -v $PWD:/var/lib/duniter/ duniter/duniter-v2s:v0.1.0 key generate-node-key --file /var/lib/duniter/node.key` +- In the same folder, create a `.env` file that defime environment variables `SERVER_DOMAIN` and `PEER_ID`: +``` +SERVER_DOMAIN=YOUR_DOMAIN +PEER_ID=Your node peer id +``` + +Your `PEER_ID` shoud be generated with this command:Â `docker run --rm -it --entrypoint duniter -v $PWD:/var/lib/duniter/ duniter/duniter-v2s:v0.1.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 .` -- `docker-compose up -d` to start your node +- `docker-compose up -d -f gdev-mirror.docker-compose.yml` to start your node ### Reverse-proxy part (with Nginx) @@ -67,7 +71,7 @@ To go further, read [How to become a (black)smith](./smith.md) ## Upgrade your node with minimal interruption 1. Modify docker image tag on your compose file -2. Run `docker compose pull`, this will pull the new image. -3. Run `docker compose up -d --remove-orphans`, this will recreate the container -4. Verify that your node restarted well `docker compose logs duniter-rpc` +2. Run `docker-compose pull`, this will pull the new image. +3. Run `docker-compose up -d --remove-orphans`, this will recreate the container +4. Verify that your node restarted well `docker-compose logs duniter-rpc` 5. Remove the old image `docker images rmi duniter/duniter-v2s:OLD_TAG` -- GitLab