You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+2-7Lines changed: 2 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -54,10 +54,10 @@ The architecture of the mini-gateway is currently simple and straightforward.
54
54
55
55
### Control Center
56
56
-[x] Web GUI - Control Panel
57
-
-[ ] Web GUI - Live Monitoring
57
+
-[x] Web GUI - Live Monitoring
58
+
-[x] Robust Logging integration
58
59
-[ ] CLI - Control Panel
59
60
-[ ] CLI - Live Monitoring (looks like htop)
60
-
-[x] Robust Logging integration
61
61
62
62
### Core Features
63
63
-[x] (proxy) HTTP/HTTPS
@@ -94,8 +94,3 @@ Each sub-repository within this project is designed to be standalone. This means
94
94
|`router-api`| Provides an API interface for managing and configuring the router. | Intended for internal use only. Not designed for external consumption. |
95
95
|`router-cli`| Command-line interface for interacting with and managing the router. | Useful for quick configuration and debugging. |
96
96
|`router-gui`| Graphical user interface for managing the router. | Designed for internal use. Should not be exposed to public networks. |
97
-
98
-
## Connectivity and Network Requirements
99
-
100
-
- The system must operate within a private and secure network. Exposing the applications or the database to public networks is not recommended and could lead to security vulnerabilities.
101
-
- The API or GUI provided by the system is intended strictly for internal use and is not designed for external consumption. Ensure that access is restricted to authorized users within the secure network.
0 commit comments