SSH clone directions

projects.md

@@ -37,7 +37,9 @@ involve some setup (like installing docker) on the VM.
 For later projects, we'll share details about how to do use cloud
 resources.
 
-## Project Repository Creation
+## Project Repository
+
+### Creation
 
 At the start of each project, you must submit the [partner
 form](https://tyler.caraza-harter.com/cs544/s25/forms.html).  This
@@ -45,8 +47,22 @@ will indicate whether or now you have a partner (and if so, who).
 Upon a valid a submission, we'll create a repo for you and your
 partner (if any) on GitLab and email you a link.
 
-## Project Setup
+### Clone
+
+You will want to clone your new repo to your VM.  There are multiple
+ways to authenticate.  One is via SSH key:
+
+1. on your VM, run `ssh-keygen` to generate a new key, following the steps indicated
+2. print the key with `cat ~/.ssh/id_ed25519.pub`, then copy it
+3. go to https://git.doit.wisc.edu/-/user_settings/ssh_keys
+4. click "Add new key"
+5. paste the key you copied, give it any title you wish, and optionally specify an expiration
+6. find your new repo (you can navigate from https://git.doit.wisc.edu/cdis/cs/courses/cs544)
+7. click the "Code" dropdown
+8. copy the "Clone with HTTPS" URL
+9. on your VM, run `git clone URL` (replacing "URL" with the one you copied)
 
+<!--
 To clone your GitLab repository on a VM, you can run the following command:
 ```bash
 git clone https://oauth2:$GITLAB_ACCESS_TOKEN@repo_url
@@ -94,6 +110,7 @@ You can double check that the `env` variable was saved with:
 ```bash
 echo $GITLAB_ACCESS_TOKEN
 ```
+-->
 
 ### Environment
 If one does not already exist for your project, create a `venv`: