Impose resource constraints on demos

Signed-off-by: Daniel Moore <[email protected]>

.env

@@ -1 +1 @@
-TAG=0.0.6
+TAG=0.0.7

README.md

@@ -51,6 +51,10 @@ The use cases supported by the three demos are summarized in conceptual block di
     - 🚨 Two EVSE Charging ⚡: `curl https://raw.githubusercontent.com/everest/everest-demo/main/demo-two-evse.sh | bash`
     - 🚨 E2E Automated Tests ⚡: `curl https://raw.githubusercontent.com/everest/everest-demo/main/demo-automated-testing.sh | bash`
 
+#### Demo Notes
+EVerest is designed with embedded applications in mind. To illustrate this, we've imposed maximum CPU usage and RAM constraints of 100% (1 core) and 1024MB, respectively, in each of the demos. Even on modest desktop hardware, these constraints should only result in slightly longer boot times.
+The resource constraints for a demo can be changed in its Docker Compose file (the file downloaded in "STEP 1" below).
+
 ### STEP 2: Interact with the demo
 - Open the `nodered` flows to understand the module flows at http://127.0.0.1:1880
 - Open the demo UI at http://127.0.0.1:1880/ui

docker-compose.admin-panel.yml

@@ -8,6 +8,11 @@ services:
 
   manager:
     image: ghcr.io/everest/everest-demo/manager:${TAG}
+    deploy:
+      resources:
+        limits:
+          cpus: '1.0'
+          memory: 1024mb
     depends_on:
       - mqtt-server
     environment:

docker-compose.iso15118-dc.yml

@@ -10,6 +10,11 @@ services:
 
   manager:
     image: ghcr.io/everest/everest-demo/manager:${TAG}
+    deploy:
+      resources:
+        limits:
+          cpus: '1.0'
+          memory: 1024mb
     depends_on:
       - mqtt-server
     environment:

docker-compose.two-evse.yml

@@ -8,6 +8,11 @@ services:
 
   manager:
     image: ghcr.io/everest/everest-demo/manager:${TAG}
+    deploy:
+      resources:
+        limits:
+          cpus: '1.0'
+          memory: 1024mb
     depends_on:
       - mqtt-server
     environment:

docker-compose.yml

@@ -8,6 +8,11 @@ services:
 
   manager:
     image: ghcr.io/everest/everest-demo/manager:${TAG}
+    deploy:
+      resources:
+        limits:
+          cpus: '1.0'
+          memory: 1024mb
     depends_on:
       - mqtt-server
     environment: