From ede308fe3ddbb75865d2126a7e23ac93cf60905c Mon Sep 17 00:00:00 2001 From: eriknordman <66556956+eriknordman@users.noreply.github.com> Date: Sun, 7 Jun 2020 07:39:12 -0500 Subject: [PATCH 1/3] suggestions for reinstall fix info based on help from yunshi --- docs/gcp/getting-started-on-gcp.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/docs/gcp/getting-started-on-gcp.md b/docs/gcp/getting-started-on-gcp.md index 8b934798..f465305e 100644 --- a/docs/gcp/getting-started-on-gcp.md +++ b/docs/gcp/getting-started-on-gcp.md @@ -70,4 +70,9 @@ You can specify with which [Machine Type](https://cloud.google.com/compute/docs/ ```sh darknode up --name my-first-darknode --gcp --gcp-credentials PATH_TO_YOUR_DOWNLOADED_JSON_FILE --gcp-machine-type f1-micro -``` \ No newline at end of file +``` + +### How to fix a faulty installation/deploy or reinstall + +You can use the configuration file to fix a registred darknode that didn't deploy right or for some other reason does'nt connect. simply deploy another darknode without registering, then copy the config.json file from the faulty installation to the new darknode installation both locally and remote. locally the file will be located on ```~/.darknode/darknodes/YourNodeName/config.json``` and remotely ```/home/darknode/config.json``` +Once copied the darknode should atuomatically connect. From 23d4d0a1106c1f378952b6f4a952fe6f6c2ca881 Mon Sep 17 00:00:00 2001 From: Loong Date: Mon, 29 Jun 2020 09:52:34 +1000 Subject: [PATCH 2/3] fix spelling mistakes --- docs/gcp/getting-started-on-gcp.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/gcp/getting-started-on-gcp.md b/docs/gcp/getting-started-on-gcp.md index f465305e..0a7b1c01 100644 --- a/docs/gcp/getting-started-on-gcp.md +++ b/docs/gcp/getting-started-on-gcp.md @@ -74,5 +74,5 @@ darknode up --name my-first-darknode --gcp --gcp-credentials PATH_TO_YOUR_DOWNLO ### How to fix a faulty installation/deploy or reinstall -You can use the configuration file to fix a registred darknode that didn't deploy right or for some other reason does'nt connect. simply deploy another darknode without registering, then copy the config.json file from the faulty installation to the new darknode installation both locally and remote. locally the file will be located on ```~/.darknode/darknodes/YourNodeName/config.json``` and remotely ```/home/darknode/config.json``` +You can use the configuration file to fix a registered node that didn't deploy right or doesn't connect. Simply deploy another node without registering, then copy the `config.json` file from the faulty installation to the new node installation both locally and remote. Locally the file will be located on ```~/.darknode/darknodes/YourNodeName/config.json``` and remotely ```/home/darknode/config.json``` Once copied the darknode should atuomatically connect. From f6dc1fe3c5e19bffca83b148c242c15a317ad3cb Mon Sep 17 00:00:00 2001 From: Loong Date: Mon, 29 Jun 2020 09:53:44 +1000 Subject: [PATCH 3/3] fix more spelling mistakes --- docs/gcp/getting-started-on-gcp.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/docs/gcp/getting-started-on-gcp.md b/docs/gcp/getting-started-on-gcp.md index 0a7b1c01..8475a43b 100644 --- a/docs/gcp/getting-started-on-gcp.md +++ b/docs/gcp/getting-started-on-gcp.md @@ -74,5 +74,4 @@ darknode up --name my-first-darknode --gcp --gcp-credentials PATH_TO_YOUR_DOWNLO ### How to fix a faulty installation/deploy or reinstall -You can use the configuration file to fix a registered node that didn't deploy right or doesn't connect. Simply deploy another node without registering, then copy the `config.json` file from the faulty installation to the new node installation both locally and remote. Locally the file will be located on ```~/.darknode/darknodes/YourNodeName/config.json``` and remotely ```/home/darknode/config.json``` -Once copied the darknode should atuomatically connect. +You can use the configuration file to fix a registered node that didn't deploy right or doesn't connect. Simply deploy another node without registering, then copy the `config.json` file from the faulty installation to the new node installation both locally and remote. Locally the file will be located on `~/.darknode/darknodes/YourNodeName/config.json` and remotely `/home/darknode/config.json`. Once copied, the node and CLI should automatically connect.