https://github.com/nikhil-prabhu/ergosphere

A reactive, event-driven push replication daemon for Pi-hole v6 replica setups.
https://github.com/nikhil-prabhu/ergosphere

daemon dns pi-hole pihole raspberry-pi replication rust sync

Last synced: 7 days ago
JSON representation

A reactive, event-driven push replication daemon for Pi-hole v6 replica setups.

• Host: GitHub
• URL: https://github.com/nikhil-prabhu/ergosphere
• Owner: nikhil-prabhu
• License: gpl-3.0
• Created: 2026-05-20T16:58:29.000Z (about 1 month ago)
• Default Branch: main
• Last Pushed: 2026-06-05T13:26:56.000Z (27 days ago)
• Last Synced: 2026-06-05T15:15:11.432Z (27 days ago)
• Topics: daemon, dns, pi-hole, pihole, raspberry-pi, replication, rust, sync
• Language: Rust
• Homepage:
• Size: 184 KB
• Stars: 0
• Watchers: 0
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

          
# ergosphere

A reactive, event-driven push replication daemon for Pi-hole v6 replica setups.

> ⚠️ **Development Status**: This project is in early development. The core synchronization engine and async event loops

> are fully operational, but some quirks are still being ironed out. Expect significant changes and potential

> instability.

> Use with caution.

## Key Features

- **Reactive Architecture**: Built on an event-driven model, `ergosphere` reacts to changes in the Pi-hole database and

  filesystem in real-time, ensuring that replicas are always up-to-date with minimal latency.

- **Recursive Event Debouncing**: Features a self-resetting async sleep window to aggregate rapid cascading file writes

  into a single optimized sync sequence.

- **Reduced Network Overhead**: By batching updates and leveraging local filesystem checks rather than constant polling,

  `ergosphere` minimizes unnecessary network traffic and database queries.

- **Lightweight and Efficient**: Designed to run on low-resource environments, making it ideal for Raspberry Pi setups

  commonly used with Pi-hole.

## Architecture Overview

Unlike other sync scripts that rely on cron-job schedules or constant polling, `ergosphere` operates on a reactive event

loop. It listens for filesystem events on core Pi-hole files (like `gravity.db`), triggering

synchronization processes only when necessary. This approach allows for more efficient resource usage and faster

replication across multiple Pi-hole instances.

1. **Monitor:** A background worker thread tracks filesystem events inside the primary Pi-hole filesystem.

2. **Debounce:** When a change is detected, a self-resetting async sleep window is initiated. If additional changes

   occur during this window, the timer resets, allowing for multiple rapid changes to be consolidated into a single sync

   operation.

3. **Validate:** Once the directory goes quiet, the daemon checks the local modification attributes. If the aggregate

   checksum matches the memory registry, execution short-circuits.

4. **Replicate**: If a real state shift is verified, `ergosphere` triggers a single-flight network pipeline: pulling a

   Teleporter binary from the primary API, distributing it to replicas, and forcing individual thread-safe gravity table

   rebuilds over chunked HTTP streams.

## Configuration

Details on configuration options can be found in

the [wiki](https://github.com/nikhil-prabhu/ergosphere/wiki/Configuration).