Update desktop guide for Windows (#1292)
* Add Windows screenshots to desktop guide
This commit is contained in:
Susmitha Girumala authored and 
GitHub committed
1 parent
ad8983e246
commit
0b819d248e
18 files changed
+116
-14
No files matched your search
@@ -8,8 +8,8 @@ description: |-
|
||||
# Boundary Desktop
|
||||
|
||||
Boundary Desktop is a standalone application that provides a simple interface
|
||||
for browsing and connecting to targets on your local computer (macOS currently
|
||||
supported). Launch a session in Boundary Desktop and then make a connection
|
||||
for browsing and connecting to targets on your local computer (macOS and Windows
|
||||
currently supported). Launch a session in Boundary Desktop and then make a connection
|
||||
using your favorite tooling!
|
||||
|
||||
## Getting Started
|
||||
@@ -23,25 +23,76 @@ $ boundary dev
|
||||
|
||||
### Install Boundary Desktop
|
||||
|
||||
1. Download the latest .dmg installer from our [releases page](https://releases.hashicorp.com/boundary-desktop). Alternatively, if you're a homebrew user, you can run `brew install hashicorp-boundary-desktop`
|
||||
1. Double-click the downloaded .dmg to run the installer
|
||||
1. Drag and drop Boundary into the applications folder
|
||||
|
||||
1. Download the latest .dmg installer or .exe archive from our [releases page](https://releases.hashicorp.com/boundary-desktop). Alternatively, if you're a homebrew user, you can run `brew install hashicorp-boundary-desktop`
|
||||
1. In macOS, double-click the downloaded .dmg to run the installer by draggin and dropping Boundary into the applications folder
|
||||
|
||||
1. In Windows, extract downloaded archive and find .exe to launch
|
||||
|
||||
### Run Boundary Desktop
|
||||
|
||||
1. Open the Boundary Desktop application
|
||||
|
||||
|
||||
<Tabs>
|
||||
<Tab heading="MacOS">
|
||||
|
||||
|
||||
|
||||
</Tab>
|
||||
<Tab heading="Windows">
|
||||
|
||||
|
||||
|
||||
</Tab>
|
||||
</Tabs>
|
||||
|
||||
1. You'll be prompted for the Boundary server origin, this is the URL for the client
|
||||
to connect to the Boundary API. If you are running a local `dev` mode server, this
|
||||
URL will be `http://localhost:9200`
|
||||
|
||||
|
||||
<Tabs>
|
||||
<Tab heading="MacOS">
|
||||
|
||||
|
||||
|
||||
</Tab>
|
||||
<Tab heading="Windows">
|
||||
|
||||
|
||||
|
||||
</Tab>
|
||||
</Tabs>
|
||||
|
||||
1. You can now login to Boundary. We're using a `dev` mode server in this example with the
|
||||
username `admin` and the password `password`
|
||||
|
||||
|
||||
<Tabs>
|
||||
<Tab heading="MacOS">
|
||||
|
||||
|
||||
|
||||
</Tab>
|
||||
<Tab heading="Windows">
|
||||
|
||||
|
||||
|
||||
</Tab>
|
||||
</Tabs>
|
||||
|
||||
1. After logging in, you should see the targets your user is authorized to connect to. Since
|
||||
we are using a `dev` mode server we see the default generated target for `127.0.0.1:22`
|
||||
|
||||
|
||||
<Tabs>
|
||||
<Tab heading="MacOS">
|
||||
|
||||
|
||||
|
||||
</Tab>
|
||||
<Tab heading="Windows">
|
||||
|
||||
|
||||
|
||||
</Tab>
|
||||
</Tabs>
|
||||
|
||||
### Connect!
|
||||
|
||||
@@ -49,10 +100,35 @@ $ boundary dev
|
||||
|
||||
1. Click on `connect` next to the default target. A pop-up window will display the local
|
||||
address of the proxy and the ephemeral port for the session
|
||||
|
||||
|
||||
<Tabs>
|
||||
<Tab heading="MacOS">
|
||||
|
||||
|
||||
|
||||
</Tab>
|
||||
<Tab heading="Windows">
|
||||
|
||||
|
||||
|
||||
</Tab>
|
||||
</Tabs>
|
||||
|
||||
1. Navigate to the `Sessions` pane and you'll see this session is in `pending` state because we
|
||||
haven't made a connection to it yet (but will!)
|
||||
|
||||
|
||||
<Tabs>
|
||||
<Tab heading="MacOS">
|
||||
|
||||
|
||||
|
||||
</Tab>
|
||||
<Tab heading="Windows">
|
||||
|
||||
|
||||
|
||||
</Tab>
|
||||
</Tabs>
|
||||
|
||||
-> The next step assumes you have a SSH server running that the default target will connect to.
|
||||
|
||||
@@ -70,7 +146,33 @@ $
|
||||
```
|
||||
|
||||
1. Navigate back to the sessions view and you'll see this session is now active
|
||||
|
||||
|
||||
<Tabs>
|
||||
<Tab heading="MacOS">
|
||||
|
||||
|
||||
|
||||
</Tab>
|
||||
<Tab heading="Windows">
|
||||
|
||||
|
||||
|
||||
</Tab>
|
||||
</Tabs>
|
||||
|
||||
1. Click `Cancel` to cancel the session and you'll see the status go to `canceling` briefly, then `terminated`
|
||||
|
||||
|
||||
<Tabs>
|
||||
<Tab heading="MacOS">
|
||||
|
||||
|
||||
|
||||
</Tab>
|
||||
<Tab heading="Windows">
|
||||
|
||||
|
||||
|
||||
</Tab>
|
||||
</Tabs>
|
||||
|
||||
1. Navigate back to the CLI and you'll see your SSH session has closed
|
||||
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
Binary file not shown.
|
After Width: | Height: | Size: 33 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 41 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 34 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 53 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 104 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 47 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 33 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 30 KiB |
Reference in new issue
Block a user