firegex/backend
2025-02-25 11:18:30 +01:00
..
binsrc TCP packet used in matching fixed 2025-02-25 11:18:30 +01:00
modules regex checked by hyperscan directly with error messages 2025-02-18 21:20:19 +01:00
routers regex checked by hyperscan directly with error messages 2025-02-18 21:20:19 +01:00
utils firewall fix, preparing for minor release 2025-02-18 14:37:11 +01:00
app.py User-Space thread balancing + refactoring 2025-02-16 16:33:34 +01:00
docker-entrypoint.sh c++ refactoring, init pypi projects, gh action added 2025-02-09 22:43:54 +01:00
README.md Update README 2022-07-22 01:12:54 +02:00
requirements.txt removed fastapi_socketio + general improves 2025-02-12 01:16:10 +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 TCP proxy filter

Read the documentation of the API going at /docs path and see the automatic documentation generated by FastAPI

GO BACK