Merge pull request #263 from gridai/sup-485-artifacts-hit-a-403-forbidden-error-2

Sup 485 artifacts hit a 403 forbidden error 2

Author: alexandercort

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

@@ -3,6 +3,10 @@ title: Accessing Artifacts
 sidebar_label: Accessing Artifacts
 ---
 
+:::note
+Please avoid using special characters in your artifact names. Grid may not be able to sync artifacts to long-term storage if the name contains percent signs, ampersands, or other special characters. The safest characters to use in your artifact names are alphanumerics, the hyphen, the underscore, and the period.
+:::
+
 # Artifacts
 Artifacts are the output produced by the training process.
 

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

@@ -182,6 +182,12 @@ You need to do this step **only once**
 # make the ssh key (if you don't have one)
 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 key_1 ~/.ssh/grid_ssh_creds.pub
 ```
@@ -230,7 +236,7 @@ Once the session is ready, you have three options to interact with it:
 - ssh from your local
 - ssh + VSCode
 
-Let's login to the Session via SSH.
+Let's login to the Session via SSH. 
 
 ```yaml
 grid session ssh resnet-debugging