Migration mapping keys v5 -> v6

[pivago]

Hi guys,

I need the equivalent keys from setupVars.conf to pihole.toml:

# IPV4_ADDRESS
# IPV6_ADDRESS

what are these both keys in pihole.toml?

Thanks

# Mapping (v5 → v6):
# setupVars.conf key     → pihole.toml key
# PIHOLE_DNS_1           → dns.upstreams
# DNS_FQDN_REQUIRED      → dns.domainNeeded + dns.expandHosts
# DNS_BOGUS_PRIV         → dns.bogusPriv
# DNSSEC                 → dns.dnssec
# PIHOLE_INTERFACE       → dns.interface
# DNSMASQ_LISTENING      → dns.listeningMode
# QUERY_LOGGING          → dns.queryLogging
# REV_SERVER             → dns.revServers
# REV_SERVER_CIDR        → as part of dns.revServers
# REV_SERVER_TARGET      → as part of dns.revServers
# REV_SERVER_DOMAIN      → as part of dns.revServers
# CACHE_SIZE             → dns.cache.size
# BLOCKING_ENABLED       → dns.blocking.active
# BLOCK_ICLOUD_PR        → dns.specialDomains.iCloudPrivateRelay
# MAXDBDAYS              → database.maxDBdays
# DBINTERVAL             → database.DBinterval
# WEBPASSWORD            → webserver.api.pwhash
# PRIVACY_LEVEL          → misc.privacylevel

# IPV4_ADDRESS           → ????
# IPV6_ADDRESS           → ????
# INSTALL_WEB_SERVER     → removed
# INSTALL_WEB_INTERFACE  → removed
# LIGHTTPD_ENABLED       → removed
# webserver.threads      → 0 (new key)

[Bucking_Horn]

@pivago

I need the equivalent keys from setupVars.conf to pihole.toml:

# IPV4_ADDRESS
# IPV6_ADDRESS

Those keys have been retired years ago with the introduction of Pi-hole's automated IP blocking mode when Pi-hole FTL v5.8, Web v5.5 and Core v5.3 released in 2021.

You usually don't need to overwrite that automated behaviour.
Unless you'd be running your Pi-hole as a Docker container in bridge network mode?

[pivago]

Thanks Bucking_Horn to let me know about the important changes.

I do not use Docker, so it is fine for me now without those two keys.