Skip to content
Théophile Diot
fren
Navigation menu
fren
All work

2021-presentOpen source maintenanceMaintainer at Bunkerity

BunkerWeb

The problem

A web application firewall can become another specialist system to configure and operate. BunkerWeb has to expose strong protection without forcing every team to become an NGINX or security expert first.

Decisions

BunkerWebDecision 1 of 4

Decision
Start from secure defaults and make configuration explicit.
Consequence
A stricter first run, and more questions to answer in public whenever a safe default blocks something a team expected to work.

BunkerWebDecision 2 of 4

Decision
Support the environments teams already use, from Linux packages to Kubernetes.
Consequence
Every release has to stay correct across four install surfaces, and their documentation can drift apart.

BunkerWebDecision 3 of 4

Decision
Treat the web interface, API, documentation, releases, and plugin surface as one product.
Consequence
A change is only finished when all five surfaces agree, so fewer changes land per release.

BunkerWebDecision 4 of 4

Decision
Keep public support discussions detailed enough to help the next operator too.
Consequence
Answering costs more than closing, and that time comes out of the same week as the code.

Outcome

For 1.6.14, I fixed a setup-wizard compatibility check that silently discarded later settings edits. Existing wizard-created services accept those edits without a migration. Forms submitted after session expiry also explain that changes were not saved. Public follow-up: 24 August 2026.

Evidence and scope

This page describes public project capabilities and maintainership. It does not expose customer deployments or private infrastructure.

This site is served behind BunkerWeb.