lovelaze/nebula-sync
Synchronize configuration of multiple Pi-hole v6.x instances. observed · 2026-10-21
Health v2 · maintenance only
91/100
- Activity 100
- Release rhythm 100
- Longevity 57
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-10-21. Adoption (stars, forks) is never an input.
- gap_med: 7
- age_days: 808
- days_rel: 0
- days_push: 0
- n_releases_24m: 14
Adoption not part of the score
1647 stars · 46 forks observed · 2026-10-21
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
nebula-sync is a Go-based tool that synchronizes configuration across multiple Pi-hole v6.x instances, using a primary/replica model. It supports full Teleporter-based sync or selective feature sync, and can run on a cron schedule via binary or Docker.
Use cases
- keep multiple pi-hole instances in sync
- replicate pihole dns blocklists to secondary servers
- schedule automatic pihole config replication with cron
- run pihole high availability with primary and replicas
- sync pihole settings via docker compose
- full teleporter export import between pihole nodes
When to choose
- you run two or more Pi-hole v6.x instances and want them to share configuration
- you want scheduled, automated replication of DNS blocking config
- you prefer a lightweight Docker or single-binary deployment
When to avoid
- you run a single Pi-hole instance
- you use Pi-hole v5.x or older
- you need real-time bidirectional sync rather than primary-to-replica
Facets
cli-tool · maturity active
deployment configuration-management cli networking networking self-hosted cli go pi-hole dns replication sync cron teleporter devops automation docker linux macos
1 source
- readme: https://github.com/lovelaze/nebula-sync · fetched 2026-10-21 · 966ea81226d0
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| lovelaze/nebula-sync | main | 91 |
For agents
markdown · JSON · MCP: product_card(name="lovelaze/nebula-sync")
Data as of 2026-10-19T08:05:51.212177+00:00 · Report a problem