# lovelaze/nebula-sync

Synchronize configuration of multiple Pi-hole v6.x instances.

Repository: https://github.com/lovelaze/nebula-sync
Canonical: https://ross.abutalabs.com/products/nebula-sync
Language: Go
License: MIT
License Family: permissive
Topics: dns, docker, golang, pi-hole, pihole, replication, sync
Last push: 2026-08-20T19:01:36+00:00

## Health v2 (maintenance only)
Score: 84/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 98, release rhythm 82, longevity 54
- inputs: {"age_days": 760, "days_push": 13, "days_rel": 120, "gap_med": 6.5, "n_releases_24m": 15}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1603, forks 44 (observed 2026-08-28T04:05:09.838762+00:00)

## What it is
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
- artifact type: cli-tool
- maturity: active
- function: deployment, configuration-management, cli, networking
- domain: networking, self-hosted
- platform: cli, go
- tags: pi-hole, dns, replication, sync, cron, teleporter, devops, automation, docker, linux, macos

## Member repositories
- lovelaze/nebula-sync (main) score 84

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:05:09.838762+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T03:52:23.459695+00:00, confidence not recorded.
  - readme: https://github.com/lovelaze/nebula-sync (fetched 2026-08-28T04:05:09.838762+00:00, sha 966ea81226d0)
- Data as of 2026-08-30T08:39:29.467469+00:00.