I had an odd memory issue. I'll attach gradle properties to grant mor…

…e memory. I assume gradle daemons don't die after finishing on client?

README.md

@@ -126,7 +126,7 @@ and wait for an output in standard output saying `Ready to accept connections at
 After verifying that the level-sites are ready, the next step is to
 start the server site. To do this, run the following command.
 
-    kubectl apply -f k8/server_site
+    kubectl apply -f k8/server
 
 To verify that the server site is ready, use the following command to confirm the server_site is _running_
 and check the logs to confirm we see `Server ready to get public keys from client-site` so we can exit and run the client.

gradle.properties

@@ -0,0 +1,17 @@
+# Project-wide Gradle settings.
+
+# IDE (e.g. Android Studio) users:
+# Gradle settings configured through the IDE *will override*
+# any settings specified in this file.
+
+# For more details on how to configure your build environment visit
+# http://www.gradle.org/docs/current/userguide/build_environment.html
+
+# Specifies the JVM arguments used for the daemon process.
+# The setting is particularly useful for tweaking memory settings.
+org.gradle.jvmargs=-Xmx4096m
+
+# When configured, Gradle will run in incubating parallel mode.
+# This option should only be used with decoupled projects. More details, visit
+# http://www.gradle.org/docs/current/userguide/multi_project_builds.html#sec:decoupled_projects
+# org.gradle.parallel=true