Update README.md
This commit is contained in:
parent
de8f6d90f3
commit
4590fdadbe
@ -25,6 +25,9 @@ Seashell can integrate with Docker to provide remote shell access into a contain
|
|||||||
```bash
|
```bash
|
||||||
ssh user:docker.example@ssh.example.com
|
ssh user:docker.example@ssh.example.com
|
||||||
```
|
```
|
||||||
|
|
||||||
|
See the [docker](https://gitea.elara.ws/Elara6331/seashell/wiki/Backends#docker) documentation for more info.
|
||||||
|
|
||||||
### Nomad
|
### Nomad
|
||||||
|
|
||||||
Seashell can integrate with a Nomad cluster to provide remote shell access into a Nomad allocation. For example, with a route configured to match `nomad\\.(.+)`, you can use the following `ssh` command to get a shell in the first allocation in the `example` job:
|
Seashell can integrate with a Nomad cluster to provide remote shell access into a Nomad allocation. For example, with a route configured to match `nomad\\.(.+)`, you can use the following `ssh` command to get a shell in the first allocation in the `example` job:
|
||||||
@ -39,6 +42,8 @@ If your job has several tasks, you can specify the task you want like so:
|
|||||||
ssh user:nomad.example.mytask@ssh.example.com
|
ssh user:nomad.example.mytask@ssh.example.com
|
||||||
```
|
```
|
||||||
|
|
||||||
|
See the [nomad](https://gitea.elara.ws/Elara6331/seashell/wiki/Backends#nomad) documentation for more info.
|
||||||
|
|
||||||
### Serial
|
### Serial
|
||||||
|
|
||||||
Seashell can provide remote access to a physical serial port. For example, with a route configured to match `serial\\.(.+)`, you can use the following `ssh` command to get a access to `/dev/ttyS0`:
|
Seashell can provide remote access to a physical serial port. For example, with a route configured to match `serial\\.(.+)`, you can use the following `ssh` command to get a access to `/dev/ttyS0`:
|
||||||
@ -53,6 +58,8 @@ If the baud rate and mode are unknown beforehand, you can specify them in the ss
|
|||||||
ssh user:serial.ttyS0.115200.8n1@ssh.example.com
|
ssh user:serial.ttyS0.115200.8n1@ssh.example.com
|
||||||
```
|
```
|
||||||
|
|
||||||
|
See the [serial](https://gitea.elara.ws/Elara6331/seashell/wiki/Backends#serial) documentation for more info.
|
||||||
|
|
||||||
### Proxy
|
### Proxy
|
||||||
|
|
||||||
Seashell can proxy another SSH server. In this case, your client will authenticate to seashell and then seashell will authenticate to the target server, so you should provide seashell with a private key to use for authentication and encryption. If you don't provide this, seashell will ask the authenticating user for the target server's password.
|
Seashell can proxy another SSH server. In this case, your client will authenticate to seashell and then seashell will authenticate to the target server, so you should provide seashell with a private key to use for authentication and encryption. If you don't provide this, seashell will ask the authenticating user for the target server's password.
|
||||||
@ -62,3 +69,5 @@ The proxy backend takes no extra arguments, so the `ssh` command only requires y
|
|||||||
```bash
|
```bash
|
||||||
ssh user:myproxy@ssh.example.com
|
ssh user:myproxy@ssh.example.com
|
||||||
```
|
```
|
||||||
|
|
||||||
|
See the [proxy](https://gitea.elara.ws/Elara6331/seashell/wiki/Backends#proxy) documentation for more info.
|
Loading…
Reference in New Issue
Block a user