From cc47c6f13b55367d70f3a505c94163bf1091c1de Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?S=C3=A1tvik=20Karanam?=
 <89281036+skara9@users.noreply.github.com>
Date: Tue, 6 Aug 2024 15:23:12 -0400
Subject: [PATCH] clarify no submissions only works from scratch

---
 .../vm_install_using_vagrant.md               | 26 +++++++++++++------
 1 file changed, 18 insertions(+), 8 deletions(-)

diff --git a/_docs/developer/getting_started/vm_install_using_vagrant.md b/_docs/developer/getting_started/vm_install_using_vagrant.md
index 3dd12210..e4fedfab 100644
--- a/_docs/developer/getting_started/vm_install_using_vagrant.md
+++ b/_docs/developer/getting_started/vm_install_using_vagrant.md
@@ -316,7 +316,7 @@ operating system.
      users in the sample courses.*
 
 
-   * **Build without sample submissions**
+   * **Build from scratch without sample submissions**
 
      If your development work *will not require sample assignment
      submissions or autograding results*, you may prepend
@@ -324,42 +324,52 @@ operating system.
      creation of these sample submissions and their autograding and
      decrease the time to complete installation.
 
+     * On Linux or Intel-based Mac:  
+       ```
+       NO_SUBMISSIONS=1 FROM_SCRATCH=1 vagrant up --provider=virtualbox
+       ```
 
-     * On Mac or Linux:  
+     * On M-series ARM Mac:
        ```
-       NO_SUBMISSIONS=1 vagrant up --provider=...
+       NO_SUBMISSIONS=1 vagrant up --provider=qemu
        ```
 
-     * Or on Windows using `cmd`:  
+     * On Windows using `cmd`:  
        ```
        SET NO_SUBMISSIONS=1
-       vagrant up --provider=...
+       SET FROM_SCRATCH=1
+       vagrant up --provider=virtualbox
        ```
 
-       Or on Windows using PowerShell, you will have to set the environment variable differently:  
+       On Windows using PowerShell, you will have to set the environment variables differently:  
        ```pwsh
        $Env:NO_SUBMISSIONS=1
+       $Env:FROM_SCRATCH=1
        vagrant up
        ```
 
-       If you want to unset the variable later in `cmd`, you can do:  
+       If you want to unset the variables later in `cmd`, you can do:  
        ```
        SET NO_SUBMISSIONS=
+       SET FROM_SCRATCH=
        ```
 
        Or in PowerShell:  
        ```pwsh
        Remove-Item Env:\NO_SUBMISSIONS
+       Remove-Item Env:\FROM_SCRATCH
        ```
 
-       Similarly, you can check that the variable is set by doing:  
+       Similarly, you can check that the variables are set in `cmd` with:  
        ```
        SET NO_SUBMISSIONS
+       SET FROM_SCRATCH
        ```
 
        Or in PowerShell:  
        ```pwsh
        $Env:NO_SUBMISSIONS
+       $Env:FROM_SCRATCH
        ```