From 4ab2bddcff16eee0fccdbe2f473f8fe67efe0325 Mon Sep 17 00:00:00 2001 From: watacchi <35671508+watacchi@users.noreply.github.com> Date: Fri, 28 Jul 2023 18:13:56 +0900 Subject: [PATCH 1/3] fix(website): fix port number on node-runner-manual.mdx --- packages/website/pages/docs/manuals/node-runner-manual.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/packages/website/pages/docs/manuals/node-runner-manual.mdx b/packages/website/pages/docs/manuals/node-runner-manual.mdx index 2ddc7183d40..dedfb35927a 100644 --- a/packages/website/pages/docs/manuals/node-runner-manual.mdx +++ b/packages/website/pages/docs/manuals/node-runner-manual.mdx @@ -75,13 +75,13 @@ docker compose -f ./docker-compose.l3.yml --env-file .env.l3 down -v **Grimsvotn L2:** ```sh -open http://localhost:3000/d/L2ExecutionEngine/l2-execution-engine-overview +open http://localhost:3001/d/L2ExecutionEngine/l2-execution-engine-overview ``` **Eldfell L3:** ```sh -open http://localhost:3001/d/L2ExecutionEngine/l2-execution-engine-overview +open http://localhost:3002/d/L2ExecutionEngine/l2-execution-engine-overview ``` ## View all logs From 77b05c0afde7b0a8f5e170fb3d332a29b30b8874 Mon Sep 17 00:00:00 2001 From: watacchi <35671508+watacchi@users.noreply.github.com> Date: Fri, 28 Jul 2023 18:16:16 +0900 Subject: [PATCH 2/3] fix(website): wrong port number on run-a-taiko-node.mdx --- .../website/pages/docs/guides/run-a-node/run-a-taiko-node.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packages/website/pages/docs/guides/run-a-node/run-a-taiko-node.mdx b/packages/website/pages/docs/guides/run-a-node/run-a-taiko-node.mdx index 0e983568091..643397038f6 100644 --- a/packages/website/pages/docs/guides/run-a-node/run-a-taiko-node.mdx +++ b/packages/website/pages/docs/guides/run-a-node/run-a-taiko-node.mdx @@ -163,7 +163,7 @@ docker compose -f ./docker-compose.l3.yml --env-file .env.l3 up -d ### Verify node is running -A node dashboard will be running on `localhost` on the `GRAFANA_PORT` you set in your `.env` or `.env.l3` file. For a Grimsvotn L2 node that would default to: [http://localhost:3000/d/L2ExecutionEngine/l2-execution-engine-overview](http://localhost:3000/d/L2ExecutionEngine/l2-execution-engine-overview). +A node dashboard will be running on `localhost` on the `GRAFANA_PORT` you set in your `.env` or `.env.l3` file. For a Grimsvotn L2 node that would default to: [http://localhost:3001/d/L2ExecutionEngine/l2-execution-engine-overview](http://localhost:3000/d/L2ExecutionEngine/l2-execution-engine-overview). You can verify that your node is syncing by checking the **chain head** on the dashboard and seeing that it is increasing. Once the chain head matches what's on the block explorer, you are fully synced. From d5e2d10409c3a2264a13f62e86a92a4e118b13b2 Mon Sep 17 00:00:00 2001 From: Kenk Date: Fri, 28 Jul 2023 18:48:41 +0800 Subject: [PATCH 3/3] Update run-a-taiko-node.mdx --- .../website/pages/docs/guides/run-a-node/run-a-taiko-node.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packages/website/pages/docs/guides/run-a-node/run-a-taiko-node.mdx b/packages/website/pages/docs/guides/run-a-node/run-a-taiko-node.mdx index 643397038f6..4b5a2341a47 100644 --- a/packages/website/pages/docs/guides/run-a-node/run-a-taiko-node.mdx +++ b/packages/website/pages/docs/guides/run-a-node/run-a-taiko-node.mdx @@ -163,7 +163,7 @@ docker compose -f ./docker-compose.l3.yml --env-file .env.l3 up -d ### Verify node is running -A node dashboard will be running on `localhost` on the `GRAFANA_PORT` you set in your `.env` or `.env.l3` file. For a Grimsvotn L2 node that would default to: [http://localhost:3001/d/L2ExecutionEngine/l2-execution-engine-overview](http://localhost:3000/d/L2ExecutionEngine/l2-execution-engine-overview). +A node dashboard will be running on `localhost` on the `GRAFANA_PORT` you set in your `.env` or `.env.l3` file. For a Grimsvotn L2 node that would default to: [http://localhost:3001/d/L2ExecutionEngine/l2-execution-engine-overview](http://localhost:3001/d/L2ExecutionEngine/l2-execution-engine-overview). You can verify that your node is syncing by checking the **chain head** on the dashboard and seeing that it is increasing. Once the chain head matches what's on the block explorer, you are fully synced.