diff --git a/Build-Server-Virtual-Machine.md b/Build-Server-Virtual-Machine.md
index a9717e7..dfe5f45 100644
--- a/Build-Server-Virtual-Machine.md
+++ b/Build-Server-Virtual-Machine.md
@@ -1,3 +1,5 @@
+The build server virtual machine is managed by a single script named `buildVm.sh` that is in the `joeylib/scripts` folder of the JoeyLib repository.
+
 It supports:
 
 ```
@@ -40,4 +42,44 @@ MacOSX10.13.sdk.tar.xz
 MacOSX11.3.sdk.tar.xz
 ```
 
-Back these up and use them instead of the XIP files to save about a day of build time next time you run `install`. [:slight_smile:](https://a.slack-edge.com/production-standard-emoji-assets/14.0/google-medium/1f642@2x.png)
\ No newline at end of file
+Back these up and use them instead of the XIP files to save about a day of build time next time you run `install`. [:slight_smile:](https://a.slack-edge.com/production-standard-emoji-assets/14.0/google-medium/1f642@2x.png)
+
+---
+
+To perform a build, first create a user.  Do not use the same account that you used when installing the VM.
+
+```
+./buildVm.sh add User PaSsWoRd
+```
+
+Then SFTP onto the server using this new user account.  You will see a `build` folder.  In that folder, upload the code you wish to build (C and H files along with any data needed by your game).
+
+After uploading the code, upload a project file explaining the build.  Project files must be named `build.start` and contain the following:
+
+* Line 1:  Short Name of Project - 15 characters or less, 8 is ideal.  Numbers and letters only.  Start with a letter.
+* Line 2-x:  Platforms to build.  One of `iigs`, `linux32`, `linux64`, `macosx32`, `macosx64`, `macosa64`, `win32`, or `win64`.
+
+The following example would build `Warehouse` for all platforms:
+
+```
+WHouse
+iigs
+linux32
+linux64
+macosx32
+macosx64
+macosa64
+win32
+win64
+```
+
+If you just want the IIgs and Windows builds, use:
+
+```
+WHouse
+iigs
+win32
+win64
+```
+
+Once you have this file, upload it **after** all the game files to start the build.  Once the build is complete, the server will **ERASE** your source and replace it with a tarball that is the result of your build.