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.

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

Jdknives patch 1 #198

Merged
merged 2 commits into from
Mar 4, 2020
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,7 @@
- [Configure](#configure)
- [`stcp` setup](#stcp-setup)
- [`dmsgpty` setup](#dmsgpty-setup)
- [`hypervisor` setup](#hypervisor-setup)
- [Run `skywire-visor`](#run-skywire-visor)
- [Run `skywire-cli`](#run-skywire-cli)
- [Run `dmsgpty`](#run-dmsgpty)
Expand Down Expand Up @@ -138,6 +139,17 @@ Here is an example configuration for enabling the `dmsgpty` server within `skywi

For `dmsgpty` usage, refer to [#run-dmsgpty](#run-dmsgpty).

#### `hypervisor` setup

Every node can be controlled by one or more hypervisors. The hypervisor allows to control and configure multiple visors. In order to allow a hypervisor to access a visor, the address and PubKey of the hypervisor needs to be configured first on the visor. Here is an example configuration:

```json
"hypervisors":[{
"public_key":"02b72766f0ebade8e06d6969b5aeedaff8bf8efd7867f362bb4a63135ab6009775",
"address":"127.0.0.1:7080"
}],
```

### Run `skywire-visor`

`skywire-visor` hosts apps, proxies app's requests to remote visors and exposes communication API that apps can use to implement communication protocols. App binaries are spawned by the visor, communication between visor and app is performed via unix pipes provided on app startup.
Expand Down