gestion d'une config pour les ip si prod ou dev

VContainers/VApp/config/config.js

@@ -0,0 +1,12 @@
+window.APP_CONFIG = {
+    // URL du broker MQTT (WebSockets)
+    // En dev local avec le setup VContainers, utiliser 'ws://localhost:9001'
+    // En prod, utiliser l'IP du serveur, ex: 'ws://192.168.73.252:9001'
+    mqttBrokerUrl: 'ws://localhost:9001',
+
+    // IPs des buzzers
+    redBuzzerIP: '192.168.73.40',
+    blueBuzzerIP: '192.168.73.41',
+    orangeBuzzerIP: '192.168.73.42',
+    greenBuzzerIP: '192.168.73.43'
+};

VContainers/run.sh

@@ -17,7 +17,7 @@ echo "Starting NanoMQ..."
 # NanoMQ needs to expose ports for external access (e.g. VApp frontend) and be on the network for VNode
 podman run -dt --rm --network $NETWORK_NAME --name nanomq \
     -p 1883:1883 -p 9001:9001 -p 8081:8081 -p 8083:8083 -p 8883:8883 \
-    -v ./VContainers/MQTT/config/nanomq.conf:/etc/nanomq.conf \
+    -v ./VContainers/MQTT/config/nanomq.conf:/etc/nanomq.conf:Z \
     docker.io/emqx/nanomq:latest --conf /etc/nanomq.conf
 
 echo "Starting VNode..."
@@ -26,6 +26,8 @@ podman run -dt --rm --network $NETWORK_NAME --name vnode vnode:latest
 
 echo "Starting VApp..."
 # VApp (nginx) needs port 80 exposed
-podman run -dt --rm --network $NETWORK_NAME --name vapp -p 8080:80 vapp:latest
+podman run -dt --rm --network $NETWORK_NAME --name vapp -p 8080:80 \
+    -v ./VContainers/VApp/config/config.js:/usr/share/nginx/html/config.js:Z \
+    vapp:latest
 
 echo "All containers started on network $NETWORK_NAME."