last update before handover

EXAMPLE_CODE.md

@@ -1,76 +0,0 @@
-# Example Code/Flow/Design
-
-## 🔒 Securing the communication
-
-### 1. Restrict to localhost for kiosk
-
-* The kiosk UI (`:8080`) should only talk to the backend via `ws://127.0.0.1:12345` (or `wss://` if you enable TLS).
-* This ensures the touchscreen browser cannot be hijacked remotely.
-
-### 2. TLS for remote UI
-
-* For the remote UI (`:9090`), expose a WebSocket server with TLS (`wss://Pi_IP:12346`).
-* Generate a self‑signed certificate or use Let’s Encrypt if the Pi is reachable externally.
-* Qt supports `QWebSocketServer::SecureMode` with SSL certificates.
-
-```cpp
-server = new QWebSocketServer("SecureServer",
-                              QWebSocketServer::SecureMode, this);
-QSslConfiguration sslConfig;
-sslConfig.setLocalCertificate(QSslCertificate::fromPath("server.crt"));
-sslConfig.setPrivateKey(QSslKey(QFile("server.key"), QSsl::Rsa));
-server->setSslConfiguration(sslConfig);
-server->listen(QHostAddress::Any, 12346);
-
-```
-
-### 3. Authentication
-
-* Require a token or password for remote clients.
-* On connection, the client must send `{ "auth":"secret123" }` before other commands.
-* Backend rejects unauthenticated clients.
-
-***
-
-## 🖥️ Serving two UIs
-
-### Option A: Two web servers
-
-* Run a lightweight HTTP server (e.g. `QtHttpServer` or `nginx`) on the Pi.
-* Serve `dashboard_kiosk.html` at port 8080.
-* Serve `dashboard_full.html` at port 9090.
-* Both connect to the same backend WebSocket, but kiosk uses localhost only.
-
-### Option B: One server, two routes
-
-* Serve both UIs from one server, but separate routes: 
-  * `http://Pi_IP:8080/kiosk`
-  * `http://Pi_IP:8080/full`
-* Use Chromium kiosk mode on the Pi to open `/kiosk`.
-
-***
-
-## 🔄 Communication flow
-
-* **Kiosk UI (touchscreen)**
-   → Connects to `ws://127.0.0.1:12345` (no TLS, local only).
-   → Sends commands like `toggleSiren`.
-   → Receives sensor updates every few seconds.
-* **Remote UI (PC browser)**
-   → Connects to `wss://Pi_IP:12346` (TLS).
-   → Authenticates with token.
-   → Can send commands and receive updates, but with richer navigation.
-
-***
-
-## 🚀 Next Steps
-
-1. Generate TLS certs (`openssl req -new -x509 -days 365 -keyout server.key -out server.crt`).
-2. Configure Qt WebSocket server with `SecureMode` for remote clients.
-3. Serve two HTML versions (kiosk vs full) via nginx or QtHttpServer.
-4. Add authentication handshake for remote connections.
-
-***
-
-
-

INTEGRATION.md

@@ -1,86 +0,0 @@
-# HTML FRONTEND + C++ HOOKS
-
-You can definitely run your HTML dashboard in **Chromium kiosk mode** and still have it talk to your existing **C++/Qt backend**. The trick is to bridge the browser UI with your native code. Here are the main approaches:
-
-[Example Code](EXAMPLE_CODE.md)
-
-***
-
-### 🔗 Integration Options
-
-#### 1. **Local WebSocket / TCP server**
-
-* Run a lightweight server inside your C++ app (e.g. using `QtWebSockets` or `QTcpServer`).
-* Your HTML buttons call JavaScript functions that send JSON messages over WebSocket.
-* Example: 
-  ```javascript
-  function sendCommand(cmd, payload={}) {
-    socket.send(JSON.stringify({command: cmd, data: payload}));
-  }
-
-  ```
-  ```cpp
-  // Qt side
-  connect(webSocketServer, &QWebSocketServer::newConnection, this, [=](){
-      auto client = webSocketServer->nextPendingConnection();
-      connect(client, &QWebSocket::textMessageReceived, this, [=](const QString &msg){
-          QJsonDocument doc = QJsonDocument::fromJson(msg.toUtf8());
-          QString cmd = doc["command"].toString();
-          // handle command
-      });
-  });
-
-  ```
-
-#### 2. **REST API (HTTP server)**
-
-* Expose endpoints in your C++ app (`/setRainfall`, `/getStatus`, etc.).
-* HTML buttons use `fetch()` to call these endpoints.
-* Example: 
-  ```javascript
-  fetch("http://localhost:8080/setRainfall", {
-    method: "POST",
-    body: JSON.stringify({value: 12.4}),
-    headers: {"Content-Type":"application/json"}
-  });
-
-  ```
-
-#### 3. **Native Messaging (Chromium extension)**
-
-* If you need tighter integration, you can build a Chromium extension that talks to your C++ app via **Native Messaging**.
-* More complex, but allows secure communication without opening a server port.
-
-***
-
-### 🖥️ Kiosk Mode Setup
-
-* Launch Chromium with flags: 
-  ```shellscript
-  chromium --kiosk --app=file:///home/user/dashboard.html
-
-  ```
-* This runs fullscreen, hides controls, and loads your HTML UI.
-
-***
-
-### ⚙️ Recommended Path
-
-For your case (Qt backend + kiosk UI), the **WebSocket approach** is usually the cleanest:
-
-* Qt has built-in WebSocket support.
-* Easy to send structured JSON messages both ways.
-* Works offline, no need for external servers.
-
-***
-
-### 🚀 Next Step
-
-Would you like me to sketch out a **minimal working example** where:
-
-* A button in the HTML dashboard sends a command (`"toggleSiren"`)
-* Your Qt app receives it and prints/logs the action?
-
-That way you’ll see the full round-trip between Chromium kiosk and your C++ backend.
-
-[Example Code/Flow/Design](https://notes.tck.com.my/workspace/06083e3a-3e03-4e37-8857-6bd2c292ef33/U2XWNlmCHW-UKuJpwMkwK)

README.md

@@ -4,10 +4,10 @@ A modern, web-based interface for Base Station/Real-Time Unit (RTU) monitoring r
 
 ```bash
 # ONE LINE INSTALL & RUN
-curl -sL http://gitck:3000/admin/sp80/install_everything.sh | bash
+curl -sL http://tckrtuiyo:3000/tck/tck_rtu/install_everything.sh | bash
 ```
 
-[View Full Wiki](WIKI.md) | [Integration with C++](INTEGRATION.md) | [Example Code](EXAMPLE_CODE.md)
+[View full Wiki](WIKI.md)
 
 ## Features
 

flip_display.sh

@@ -1,13 +0,0 @@
-#!/bin/bash
-
-# Flip screen
-# C-Fu for TCK
-
-# Flip the display
-DISPLAY=:0 xrandr --output HDMI-1 --reflect x
-
-# Flip the touch input (using ID 7 for your specific device)
-DISPLAY=:0 xinput set-prop 7 'Coordinate Transformation Matrix' -1 0 1 0 1 0 0 0 1
-
-# Change reso
-DISPLAY=:0 xrandr --output HDMI-1 --mode 1024x600

start-rtu-dev.service

@@ -4,7 +4,7 @@ After=network.target
 #Before=nextcloud-web.service
 
 [Service]
-ExecStart=/root/rtu_v5/start.sh dev:8888
+ExecStart=/root/rtu_v4/start.sh dev:8888
 #ExecReload=/root/rtu_v4/start.sh dev:8888
 Type=simple
 Restart=always

start.sh

@@ -3,16 +3,6 @@
 # TCK RTU - Start Script
 # Interactive menu for common development commands
 
-# Flip the display horizontally, and maaaybe flip the mouse cursor+touchscreen as well
-# NOW JUST RUN ./flip_display.sh
-
-# Flip the display
-#DISPLAY=:0 xrandr --output HDMI-1 --reflect x
-
-# Flip the touch input (using ID 7 for your specific device)
-#DISPLAY=:0 xinput set-prop 7 'Coordinate Transformation Matrix' -1 0 1 0 1 0 0 0 1
-
-
 set -e
 
 # Colors