Elgato_dark/fleet
1
0
Fork 0
mirror of https://github.com/fleetdm/fleet synced 2026-05-23 08:58:41 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 111

Use https://fleet.corp.example.com as demo Fleet server address

Browse source
This commit is contained in:
Mike Arpaia 2018-05-23 22:02:55 -06:00
parent 58e0cb68cb
commit 3a6c923d8d
No known key found for this signature in database
GPG key ID: 257B170C423DE4A0
1 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
docs/cli/setup-guide.md
View file

@ -35,8 +35,8 @@ $ fleetctl config set --address https://localhost:8080 --tls-skip-verify
Now, if you were connecting to a Fleet instance for real, you wouldn't want to skip TLS certificate verification, so you might run something like:
```
$ fleetctl config set --address https://fleet.osquery.tools
[+] Set the address config key to "https://fleet.osquery.tools" in the "default" context
$ fleetctl config set --address https://fleet.corp.example.com
[+] Set the address config key to "https://fleet.corp.example.com" in the "default" context
```
## `fleetctl setup`
@ -152,8 +152,8 @@ Now run a live query again. You should notice results coming back more quickly.
If you have an existing Fleet instance (version 2.0.0 or above), then simply run `fleet login` (after configuring your local CLI context):
```
$ fleetctl config set --address https://fleet.osquery.tools
[+] Set the address config key to "https://fleet.osquery.tools" in the "default" context
$ fleetctl config set --address https://fleet.corp.example.com
[+] Set the address config key to "https://fleet.corp.example.com" in the "default" context
$ fleetctl login
Log in using the standard Fleet credentials.