ad/firegex
1
0
Fork 0
mirror of https://github.com/Av0idD4rk/firegex.git synced 2026-10-23 15:30:59 +00:00
Code Issues Packages Projects Releases Wiki Activity
75c54f0155
firegex/backend
History
Sogoss 75c54f0155 Add transparent TLS proxying and certificate management for NFProxy and NFRegex 
- Add Nginx stream proxy module for transparent TLS termination in NFProxy and NFRegex
- Add backend routes and SQLite schema for certificate management (upload, view, delete)
- Implement DNAT nftables redirection rules for deterministic TLS ports
- Add frontend React components (TLSConfigModal, TLSServiceFields) for certificate configuration
- Update Dockerfile and docker-entrypoint.sh to support Nginx stream module and sysctl forwarding
2026-07-20 12:25:30 +02:00
..
binsrc Add transparent TLS proxying and certificate management for NFProxy and NFRegex 2026-07-20 12:25:30 +02:00
modules Add transparent TLS proxying and certificate management for NFProxy and NFRegex 2026-07-20 12:25:30 +02:00
routers Add transparent TLS proxying and certificate management for NFProxy and NFRegex 2026-07-20 12:25:30 +02:00
utils Add transparent TLS proxying and certificate management for NFProxy and NFRegex 2026-07-20 12:25:30 +02:00
app.py Add transparent TLS proxying and certificate management for NFProxy and NFRegex 2026-07-20 12:25:30 +02:00
docker-entrypoint.sh Add transparent TLS proxying and certificate management for NFProxy and NFRegex 2026-07-20 12:25:30 +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

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