01. Request Flow
Incoming traffic is terminated at Nginx via TLS 1.3. Requests are then dispatched to the custom PHP router which resolves the internal view state.
Incoming traffic is terminated at Nginx via TLS 1.3. Requests are then dispatched to the custom PHP router which resolves the internal view state.
Sessions are handled in-memory via Redis. This allows for high-concurrency and ensures that experimental PHP-FPM pools don't clash with stable production data.
Fail2Ban monitors Nginx logs for malicious patterns. Private artifacts are gated behind a session-based vault with SHA-256 password hashing.