@@ -26,6 +26,10 @@ This page is also accessible via the Nebari Home Page:
26
26
- If your deployment has `jhub-apps` enabled, you can navigate to this page by selecting the `Token` option under your username in the upper righthand corner.
27
27
- If your deployment does not have `jhub-apps` enabled, you can click on the `Token` link on the top navigation bar.
28
28
29
+ Fill out the form for token creation:
30
+
31
+ 
32
+
29
33
You may add a note and expiration date to the token. You can leave the scopes field blank to give the token all the permissions that your user typically has on JupyterHub (which is the service on which Nebari is running).
30
34
31
35
## Connect to Nebari via SSH
@@ -36,7 +40,7 @@ Before you begin, you'll need to have SSH installed on your local machine. From
36
40
37
41
:::important
38
42
The syntax for `<your-nebari-domain.com>` is important - do not include `https://` or a trailing `/`. If you have the incorrect syntax, it will result in the error:
39
- ``` Could not resolve hostname <your-nebari-domain.com>: nodename nor servname provided, or not known`` `
43
+ `Could not resolve hostname <your-nebari-domain.com>: nodename nor servname provided, or not known`
40
44
:::
41
45
42
46
You will then be prompted for your password. Enter the token as the password and press `Enter`.
@@ -55,23 +59,24 @@ By default, SFTP uses the SSH protocol to authenticate and establish a secure co
55
59
56
60
Utilizing SFTP will depend on how your local machine is configured and the utility you're using for SFTP. In some cases, your SSH configuration will allow SFTP to work " out of the box" . Other times, special SFTP setup is required in your SSH configuration to allow for these connections.
57
61
Similar to `ssh`, from a terminal, use `sftp` to begin a new connection:
58
- ``` sftp <your-nebari-domain.com> -l <your-username> -p 8023`` `
62
+ `sftp <your-nebari-domain.com> -l <your-username> -p 8023`
59
63
60
64
### Transferring Files with SFTP
61
65
62
66
Downloading Files:
63
67
64
68
- Use the `get` command to download files from the remote host:
65
- - `get <remote-file>` downloads the file with the same name to the local system.
66
- - `get <remote-file> <local-file>` downloads and saves the file with a different name.
67
- - To download a directory and its contents, use `get -r <some-directory>`.
68
- - To maintain permissions and access times, use `get -Pr <some-directory>`.
69
+ - `get <remote-file>` downloads the file with the same name to the local system.
70
+ - `get <remote-file> <local-file>` downloads and saves the file with a different name.
71
+ - To download a directory and its contents, use `get -r <some-directory>`.
72
+ - To maintain permissions and access times, use `get -Pr <some-directory>`.
69
73
70
74
Uploading Files:
71
75
72
76
- Use the `put` command to upload files to the remote system:
73
- - `put <local-file>` uploads the file.
74
- - To upload a directory and its contents, use `put -r <some-directory>`.
77
+ - `put <local-file>` uploads the file.
78
+ - To upload a directory and its contents, use `put -r <some-directory>`.
79
+
75
80
## Dangerous, but useful information
76
81
77
82
:::warning
0 commit comments