Skip to content

Commit 3fbd749

Browse files
committed
Update installation instructions
Signed-off-by: Alex Ellis (OpenFaaS Ltd) <alexellis2@gmail.com>
1 parent 7d5ee07 commit 3fbd749

1 file changed

Lines changed: 2 additions & 10 deletions

File tree

docs/getting-started/install.md

Lines changed: 2 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -53,17 +53,9 @@ The installer sets up [Firecracker](https://firecracker-microvm.github.io), [Clo
5353
5454
Additional storage backends can always be enabled later by running the installer again with the appropriate flags.
5555

56-
Activate Slicer to obtain your license key:
56+
If you have a subscription for Slicer Individual, Team or Platform, then you'll have received a license key via email. Save it to ~/.slicer/LICENSE`.
5757

58-
```bash
59-
slicer activate --help
60-
61-
slicer activate
62-
```
63-
64-
For the Individual tier the a license key will be written to `~/.slicer/LICENSE` along with a GitHub token. The key will last for 30 days, but can be refreshed via `slicer activate`. When refreshing, it'll use the stored GitHub token, instead of running the device flow again.
65-
66-
For higher tiers, the license key is an API key delivered to you via email. You should save it to `~/.slicer/LICENSE`.
58+
If you're using the GitHub Sponsors bundle for SlicerVM, K3sup Pro and Superterm, then you can run `slicer activate` to obtain a key with your GitHub account. The key will last for 30 days, but can be refreshed via `slicer activate`. When refreshing, it'll use the stored GitHub token, instead of running the device flow again.
6759

6860
Next, start your first VM with the [walk through](/getting-started/walkthrough).
6961

0 commit comments

Comments
 (0)