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

Feature/config subcommand #914

Merged
merged 5 commits into from
Oct 8, 2021
Merged

Feature/config subcommand #914

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
dbcacf3
Merge remote-tracking branch 'upstream/develop' into develop
alexadhy Oct 7, 2021
3e89d23
adds config subcommand, remove config subcommand from visor subcommand
alexadhy Oct 7, 2021
c8c6b40
formatting
alexadhy Oct 7, 2021
508a12d
added checks for environment value, and edited CHANGELOG.md
alexadhy Oct 8, 2021
149daef
Merge branch 'develop' into feature/config-subcommand
jdknives Oct 8, 2021
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
3 changes: 3 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,10 +16,12 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.
- changed proxy_discovery_addr field to service_discovery
- updated UI
- removed `--public` flag from `skywire-cli visor add-tp` command
- removed `skywire-cli visor gen-config` and `skywire-cli visor update-config` subcommands.
- replaced stcp field to skywire-tcp in config and comments
- replaced local_address field to listening_address in config
- replaced port field to dmsg_port in config


### Added

- added persistent_transports field to the config and UI
Expand All @@ -28,6 +30,7 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.
- added public_autoconnect field to transport section
- added transport_setup_nodes field to transport section
- added MinHops field to V1Routing section of config
- added `skywire-cli config` subcommand

## 0.2.1 - 2020.04.07

Expand Down
8 changes: 4 additions & 4 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,14 +37,14 @@ Skywire can be statically built. For instructions check [the docs](docs/static-b
In order to expose the hypervisor UI, generate a config file with `--is-hypervisor` or `-i` flag:

```bash
$ skywire-cli visor gen-config -i
$ skywire-cli config gen -i
```

Docker container will create config automatically for you, should you want to run it manually, you can do:

```bash
$ docker run --rm -v <YOUR_CONFIG_DIR>:/opt/skywire \
skycoin/skywire:test skywire-cli gen-config -i
skycoin/skywire:test skywire-cli config gen -i
```

After starting up the visor, the UI will be exposed by default on `localhost:8000`.
Expand All @@ -55,14 +55,14 @@ Every visor can be controlled by one or more hypervisors. To allow a hypervisor
hypervisor needs to be specified in the configuration file. You can add a remote hypervisor to the config with:

```bash
$ skywire-cli visor update-config --hypervisor-pks <public-key>
$ skywire-cli config update --hypervisor-pks <public-key>
```

Or from docker image:

```bash
$ docker run --rm -v <YOUR_CONFIG_DIR>:/opt/skywire \
skycoin/skywire:test skywire-cli update-config hypervisor-pks <public-key>
skycoin/skywire:test skywire-cli config update hypervisor-pks <public-key>
```

## Run `skywire-visor`
Expand Down
Loading