Git Sync Daemon

Purpose

Provide a reusable, daemon-based git auto-sync workflow:

• - one repo list file
• one daemon process
• per-repo lock and independent failure isolation
• service management on macOS and Linux

Files

• - Engine: INLINECODE0
• Control CLI: INLINECODE1

Default Runtime Paths

• - State dir: INLINECODE2
• Repo list: INLINECODE3
• Log file: INLINECODE4

Repo Entry Format

One line per repo:

CODEBLOCK0

Supported keys:

• - remote (default origin)
• INLINECODE7 (default current branch)
• INLINECODE8 (1/0, true/false, default enabled)

Quick Start (macOS)

CODEBLOCK1

Quick Start (Linux)

CODEBLOCK2

Operations

• - Add repo: INLINECODE11
• Remove repo: INLINECODE12
• List repos: INLINECODE13
• One cycle now: INLINECODE14
• Status/log tail: INLINECODE15

Service lifecycle:

• - macOS install: INLINECODE16
• macOS uninstall: INLINECODE17
• Linux install: INLINECODE18
• Linux uninstall: INLINECODE19

Production hardening checklist

Before enabling daemon mode in production:

1. 1. SSH/auth baseline

• - Ensure service user can run non-interactive git over SSH to each remote.
• Preload host keys (ssh-keyscan / StrictHostKeyChecking=accept-new) to avoid first-run failures.
• Prefer explicit key routing in ~/.ssh/config (host/user/port/IdentityFile/IdentitiesOnly).

1. 2. Service identity consistency

• - Install service with the same user that owns repo credentials and git config.
• Verify git config --global user.name/user.email for that service user.

1. 3. Repo registration policy

• - Register only clean, intended repos.
• Keep one canonical branch per repo entry; avoid detached HEAD targets.
• Use enabled=0 for temporary pauses instead of deleting lines.

1. 4. Observability

• - Keep logs in dedicated file and rotate externally if needed.
• Validate run-once before enabling persistent service.

Safety Notes

• - The daemon does not force-push.
• Rebase conflicts are logged and isolated to the affected repo.
• If git-lfs is required by hooks but missing, that repo is skipped with explicit error log.
• On macOS launchd, PATH is expanded in both service env and daemon script to include Homebrew binaries.
• Recommended migration practice: first successful run should use baseline repos only; then gradually add more repos.