ad/firegex
1
0
Fork 0
mirror of https://github.com/Av0idD4rk/firegex.git synced 2026-10-23 16:31:00 +00:00
Code Issues Packages Projects Releases Wiki Activity
5343735129
firegex/backend
History
Minei3oat 907c85d85d Add Content-Type=plain/text for metrics endpoint 
Without the content type, prometheus will reject the metrics if no `fallback_scrape_protocol` is specified.

https://prometheus.io/docs/prometheus/3.0/migration/#scrape-protocols
https://prometheus.io/docs/instrumenting/exposition_formats/#text-based-format
2025-09-28 21:09:25 +02:00
..
binsrc fixed: packet size of mnl including packet size it-self (was causing crash sometime) and frontend updates 2025-07-28 15:45:22 +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 firegex custom host and better port config managment 2025-08-17 16:23:49 +02:00
app.py firegex custom host and better port config managment 2025-08-17 16:23:49 +02:00
docker-entrypoint.sh websocket fix + starting firegex as root if capsh fails 2025-04-12 22:15:08 +02:00
README.md README: update 2025-03-09 23:52:34 +01:00
requirements.txt Pointed to a specific brotli version on google repo due to a tmp rollback 2025-09-15 10:19:31 +02:00

README.md

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