firegex/frontend
Domingo Dirutigliano 6140fcbe81
Align the demo backend with the real nfproxy API
The stubbed `GET .../code` answered with `{ code }` while the real endpoint
is a PlainTextResponse returning the source, which is what crashed the demo
service page, and the save route was registered as POST where the real API
and the frontend both use PUT.

The seeded sample also carried a `strip_debug_header` filter that mutated
`HttpRequest.headers`. That silently does nothing: `headers` is a read-only
property over the parsed message, and nothing re-serialises it onto the wire
(a mangle forwards `current_pkt.raw_packet`, which the dict never touches).
Dropped it, leaving the one filter that behaves as shown, and brought the
filter counts and the packet counters back in line with it.
2026-09-03 18:42:37 +02:00
..
public add: frontend update 2024-10-13 01:50:52 +02:00
src Align the demo backend with the real nfproxy API 2026-09-03 18:42:37 +02:00
.env.demo Publish a browsable demo on GitHub Pages 2026-09-03 09:36:37 +02:00
bun.lock Update frontend dependencies to latest 2026-09-03 10:22:19 +02:00
index.html mantine update + passed to vite 2023-06-05 00:57:54 +02:00
package.json Update frontend dependencies to latest 2026-09-03 10:22:19 +02:00
README.md docs: update 2023-10-01 02:21:07 +02:00
tsconfig.json mantine update 2026-06-21 11:49:53 +02:00
vite.config.ts integrated and refactore docs + minor changes 2026-07-23 16:53:09 +02:00

Firegex Frontend

Firegex Frontend

The frontend of firegex is written using vite. The routing of the pages is managed by react-router 6 and the graphics is mainly managed by the framework Mantine and icons provided by React Icons. The style of the page is written with sass.

The page is auto-updated by a global timeout and also thanks to socket.io that raise an event triggering all parts of the app that requires fetch updated data from the backend, the update of these data.

GO BACK