From a4726006c9bc85f40bcca0bb5e2db7a81c9377b4 Mon Sep 17 00:00:00 2001 From: Andrew Quijano Date: Sun, 25 Jun 2023 03:05:53 +0000 Subject: [PATCH] I had an odd memory issue. I'll attach gradle properties to grant more memory. I assume gradle daemons don't die after finishing on client? --- README.md | 2 +- gradle.properties | 17 +++++++++++++++++ 2 files changed, 18 insertions(+), 1 deletion(-) create mode 100644 gradle.properties diff --git a/README.md b/README.md index ab2f671..216812f 100644 --- a/README.md +++ b/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. diff --git a/gradle.properties b/gradle.properties new file mode 100644 index 0000000..3d23eb2 --- /dev/null +++ b/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