Merge pull request #329 from gridai/dev

Docs Update

Author: oojo12

docs/features/runs/2_Analyzing Runs/3_artifacts.md

@@ -12,7 +12,9 @@ Artifacts are the output produced by the training process.
 
 ## Saving artifacts
 
-Anytime your script saves artifacts, Grid captures those for you. It does not matter which folder you save artifacts to... Grid will automatically detect them.
+Anytime your script saves new artifacts, Grid captures those for you. It does not matter which folder you save artifacts to... Grid will automatically detect them.  
+
+Grid only saves new artifacts. Any file that existed before training starts, even if modified during training, will not be saved.
 
 Grid uploads your artifacts to long-term storage while your experiment is running *and* at the end of your experiment. This is to ensure that even if your experiment crashes, your artifacts will be saved.
 

docs/features/sessions/8_how-to-ssh-into-a-session.md

@@ -12,22 +12,22 @@ Create an SSH key from the computer you'd like to connect from (skip this step i
 
 ```yaml
 # make the ssh key (if you don't have one)
-ssh-keygen -t ed25519 -C "your_email@example.com"
-or
-ssh-keygen -b 2048 -t rsa -q -N ""
+ssh-keygen -b 2048 -t rsa -f ~/.ssh/grid_ssh_creds -q -N ""
 ```
 
 ## Step 1: Add the SSH key
 
-Here we assume to have SSH keys named _ed25519.pub_, which are the default used by the command above.
-
-We're going to add the key and name it _lit_key_
+Here we use the ssh-agent to manage the keys and will add them to Grid.
 
 ```yaml
+# add the key to the ssh-agent (to avoid having to explicitly state key on each connection)
+# to start the agent, run the following
+eval $(ssh-agent)
+# then add the key
+ssh-add  ~/.ssh/grid_ssh_creds
+
 # add the keys to grid
-grid ssh-keys add lit_key ~/.ssh/id_ed25519.pub
-or
-grid ssh-keys add key_1 ~/.ssh/id_rsa.pub
+grid ssh-keys add key_1 ~/.ssh/grid_ssh_creds.pub
 ```
 
 If you go to [Grid settings](https://platform.grid.ai/#/settings?tabId=ssh), you'll see SSH keys you've added to Grid

docs/features/sessions/9_vscode-with-sessions.md

@@ -12,10 +12,16 @@ Create an ssh key from the computer you'd like to connect from (skip this step i
 
 ```yaml
 # make the ssh key (if you don't have one)
-ssh-keygen -t ed25519 -C "your_email@example.com"
+ssh-keygen -b 2048 -t rsa -f ~/.ssh/grid_ssh_creds -q -N ""
+
+# add the key to the ssh-agent (to avoid having to explicitly state key on each connection)
+# to start the agent, run the following
+eval $(ssh-agent)
+# then add the key
+ssh-add  ~/.ssh/grid_ssh_creds
 
 # add the keys to grid
-grid ssh-keys add lit_key ~/.ssh/id_ed25519.pub
+grid ssh-keys add key_1 ~/.ssh/grid_ssh_creds.pub
 ```
 
 ## Step 1: Launch a session

docs/getting-started/typical-workflow-cli-user.md

@@ -291,10 +291,7 @@ grid session ssh resnet-debugging
 ```
 
 Now link up VSCode with the Session
-
-```yaml
-grid session ssh vscode
-```
+![](/images/sessions/vscode-remote.gif)
 
 **The model**