Migrating from bunkerized
Read this if you were a bunkerized user
A lot of things changed since the last bunkerized release. If you want to do an upgrade, which we recommend you do because BunkerWeb is by far, better than bunkerized. Please read carefully this section as well as the whole documentation.
When using container-based integrations like Docker, Docker autoconf, Swarm or Kubernetes, volumes for storing data like certificates, cache or custom configurations have changed. We now have a single "bw-data" volume which contains everything and should be easier to manage than bunkerized.
We decided to drop the following features :
- Blocking "bad" referrers : we may add it again in the future
- ROOT_SITE_SUBFOLDER : we will need to redesign this in the future
Changed Authelia support
Replaced BLOCK_*, WHITELIST_* and BLACKLIST_* settings
The blocking mechanisms have been completely redesigned. We have detected that a lot of false positives came from the default blacklists hardcoded into bunkerized. That's why we now give users the possibility of choosing their own blacklists (and also whitelists) for IP address, reverse DNS, user-agent, URI and ASN, see the Blacklisting and whitelisting section of the security tuning.
Changed WHITELIST_USER_AGENT setting behavior
The new behavior of the WHITELIST_USER_AGENT setting is to disable completely security checks if the User-Agent value of a client matches any of the patterns. In bunkerized it was used to ignore specific User-Agent values when
BLOCK_USER_AGENT was set to
yes to avoid false positives. You can select the blacklist of your choice to avoid FP (see previous section).
Changed PROXY_REAL_IP_* settings
To avoid any confusion between reverse proxy and real IP, we decided to rename the
PROXY_REAL_IP_* settings, you will find more information on the subject here.