Skip to content

Make the Linux Server guide less SSH-centric#26309

Merged
ptgott merged 5 commits intomasterfrom
paul.gottschling/2023-05-15-linux-server-edit
May 19, 2023
Merged

Make the Linux Server guide less SSH-centric#26309
ptgott merged 5 commits intomasterfrom
paul.gottschling/2023-05-15-linux-server-edit

Conversation

@ptgott
Copy link
Copy Markdown
Contributor

@ptgott ptgott commented May 15, 2023

The current Linux Server guide includes instructions for accessing the server and viewing a session recording. For users who are not interested in server access, this can be irrelevant or even a turnoff. Instead of showing SSH-specific features, make the final step about registering resources using the Web UI.

ptgott added 3 commits May 16, 2023 17:33
The current Linux Server guide includes instructions for accessing the
server and viewing a session recording. For users who are not interested
in server access, this can be irrelevant or even a turnoff. Instead of
showing SSH-specific features, make the final step about registering
resources using the Web UI.
Step 4 of the Linux Server guide, which instructs the user to log in to
a cluster via `tsh`, breaks the user's focus from the Web UI
unnecessarily. `tsh` isn't complex enough to require its own step in
this guide.

For users who would like CLI access to Teleport, this change includes
the information as a Details box.
Use the term "enroll" instead.
@ptgott ptgott force-pushed the paul.gottschling/2023-05-15-linux-server-edit branch from 1be15dc to 6dd94ef Compare May 16, 2023 21:52
@ptgott
Copy link
Copy Markdown
Contributor Author

ptgott commented May 16, 2023

@rodgtr1 I incorporated some of your feedback in 6dd94ef .

The feedback I haven't incorporated:

  • I wasn't sure how to use the term "proxy" more in the guide (other than "Proxy Service", of course)
  • We'll still need to find a good diagram to use. This PR that I opened before last Friday's meeting adds the following Mermaid diagram, though it will probably need tweaking/styling if we're giving it pride of place. (We can also have someone with graphic design talent create something):
flowchart LR
subgraph private[Private network]
    direction LR
    serv1[Teleport service]
    serv2[Teleport service]
    serv3[Teleport service]
end
subgraph public[Public network]
    Developers
end
subgraph server[Linux server]
    direction RL
    auth["Auth Service"]
    proxy[Proxy Service]
    ssh[SSH Service]
    auth-- "Short-lived credentials" -->proxy
    ssh-- Reverse tunnel-->proxy
end
Developers-- tsh sessions --->server
serv1 & serv2 & serv3-- Reverse tunnel--->server
Loading

Comment thread docs/pages/get-started.mdx
Comment thread docs/pages/get-started.mdx Outdated
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since the light theme is now the default for Teleport 13, should we use that in new screenshots of the web UI?

@rodgtr1
Copy link
Copy Markdown
Contributor

rodgtr1 commented May 18, 2023

@ptgott I think this PR is perfect, with the addition of Alex's suggestions. As for diagrams, what about something like this (would get Peter to make it look better). Or is this too basic, i.e. some more details added? Trying to keep it on par with the guide.

image

@ptgott
Copy link
Copy Markdown
Contributor Author

ptgott commented May 19, 2023

@rodgtr1 What would you think of us working on the diagram in a subsequent PR? That way we can merge these easy-to-make changes and see what needs to be done in terms of getting a nice diagram together?

@rodgtr1
Copy link
Copy Markdown
Contributor

rodgtr1 commented May 19, 2023

@rodgtr1 What would you think of us working on the diagram in a subsequent PR? That way we can merge these easy-to-make changes and see what needs to be done in terms of getting a nice diagram together?

Yes, lets do that in another PR

@ptgott
Copy link
Copy Markdown
Contributor Author

ptgott commented May 19, 2023

@rodgtr1 Sounds good! Is there anything else we should do in this PR before merging?

@rodgtr1
Copy link
Copy Markdown
Contributor

rodgtr1 commented May 19, 2023

@rodgtr1 Sounds good! Is there anything else we should do in this PR before merging?

@ptgott No I think this is sufficient for now. We can mull over it for a bit and then create a new PR for any further tweaks.

@ptgott
Copy link
Copy Markdown
Contributor Author

ptgott commented May 19, 2023

@rodgtr1 👍 Do you have permissions to approve?

@rodgtr1
Copy link
Copy Markdown
Contributor

rodgtr1 commented May 19, 2023

@rodgtr1 👍 Do you have permissions to approve?

Ahh, though I did. Done.

@ptgott ptgott enabled auto-merge May 19, 2023 18:36
@ptgott ptgott added this pull request to the merge queue May 19, 2023
Merged via the queue into master with commit ae76125 May 19, 2023
@ptgott ptgott deleted the paul.gottschling/2023-05-15-linux-server-edit branch May 19, 2023 18:52
@public-teleport-github-review-bot
Copy link
Copy Markdown

@ptgott See the table below for backport results.

Branch Result
branch/v11 Failed
branch/v12 Create PR
branch/v13 Create PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants