I have no support/technical question and have seen the support category. (Be aware that direct support questions will be deleted.)
on
Which general topic do you have
I have built an open-source daemon that provides continuous file sync for headless Linux servers using nextcloudcmd. This was built for my own use, but others may find it useful as there are requests for this kind of thing in the forums.
The daemon fills the gap between the desktop client (needs a display server) and running nextcloudcmd from cron (high latency, unnecessary load).
Background:
The project grew out of a production deployment syncing files across headless Debian servers (VMs and Raspberry Pis). The original prototype used bash + inotifywait + a Python webhook listener + a systemd timer — four separate components. The Go rewrite provides all of these in a single binary.
What it does
- Watches local files via inotify — syncs immediately on local changes
- Receives Nextcloud webhook push notifications — syncs immediately on server changes
- Polls as a fallback — catches anything the event-driven layers miss
- All three feed a single event queue with deduplication and cooldown, preventing sync storms
- Runs as a systemd service with Type=notify, watchdog, and structured logging
What it needs
- nextcloudcmd (from nextcloud-desktop-cmd)
- Linux (uses inotify)
Repository
License: MIT Pre-built binaries: linux/amd64 and linux/arm64
Claude Code Developed
The project was built using Claude Code as a practical test of AI-assisted development. The full development process — decisions, mistakes, iterations — is documented transparently in the repo’s development journal and took around a day from the idea to the production code. All the documentation was produced by Claude Code as part of the guided development process.