firegex/backend
2026-07-12 18:58:57 +02:00
..
binsrc invalid request check on nfqueue updated 2026-06-18 21:00:30 +02:00
modules using name and id as pk for PyFilter when updating stats 2025-06-13 13:33:13 +02:00
routers Add Content-Type=plain/text for metrics endpoint 2025-09-28 21:09:25 +02:00
utils auto-recognize version when using cloned firegex 2026-07-12 18:58:57 +02:00
app.py additional fixes to socket binding 2025-10-01 15:37:20 +02:00
docker-entrypoint.sh additional fixes to socket binding 2025-10-01 15:37:20 +02:00
README.md README: update 2025-03-09 23:52:34 +01:00
requirements.txt using brotli 1.2 from pypi, fixed tests to py 3.14, removed from experimental pyproxy 2025-11-11 23:30:48 +01:00

Firegex backend

GO BACK

The backend of firegex is written with fastapi. The aim of the backend is to manage all the requests from the react front-end and manage also the proxy processes of the entire firewall. The fastapi webserver is responsable of deploying the react app.

Firegex Working Scheme Schematic example about how firegex manage the filters

Read the documentation of the API going at /api/docs path and see the swagger documentation of the API.

GO BACK