Pihole 6 declarative set up for adlists, whitelists, clients and groups

General
1

I'm currently migrating my home pihole set up to a docker-compose stack that I can deploy on a few different hosts and I'm seeking to provision fully configured instances which are basically clones of each other instead of the previous gravity-sync jobbie. With ansible, but that's by-the-by.

I've been able to find most of what I needed from pihole.toml after I migrated one of my hosts and was able to successfully set them up using FTLCONF_xxx vars. So far so good.

Where I'm stuck is on the following:

  • Adlists
  • Whitelists
  • Clients
  • Groups

I can't see any options on pihole.toml and as far as I can see the settings for those are all stored directly on the gravity database. I've been able to use /etc/pihole/adlists.list and /etc/pihole/whitelist.txt (for non-regex), but these feel like they could be automatic migrations from legacy stuff that might go away in the future?

What's the proper way to provision those, and clients and groups?

2

Is this because it's no longer supported?

There is also GitHub - lovelaze/nebula-sync: Synchronize configuration of multiple Pi-hole v6.x instances.

I guess this is one of the areas the container is lacking - bit of a non-commital statement here, just thinking out loud, but I wonder if we could detect a teleporter backup file moutned to the container and then utilise a POST request /teleporter endpoint of the API.

That would require at least a one time set up of an instance - but then you would just create a teleporter backup from that one and use it as part of your container build process... food for thought!

3

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.