Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

suggestions for reinstall fix info #70

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
Open

suggestions for reinstall fix info #70

Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
ede308f
suggestions for reinstall fix info
eriknordman Jun 7, 2020
23d4d0a
fix spelling mistakes
loongy Jun 28, 2020
f6dc1fe
fix more spelling mistakes
loongy Jun 28, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
7 changes: 6 additions & 1 deletion docs/gcp/getting-started-on-gcp.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
```
```

### 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.
loongy marked this conversation as resolved.
Show resolved Hide resolved