Developers lack reliable commands for file and sync events
Developers and Syncthing users want commands to run when files change, on save, or after synchronization, but they often have to configure watchers or build their own workarounds. One request describes existing file-watcher extensions as tedious to set up; a Syncthing user reports replacing inefficient or unreliable inotify scripts with a custom daemon. Cross-platform recursive watching adds another layer of complexity.
For developers and Syncthing users. Mentioned from Jun 2014 to May 2025 on GitHub.
6 different people described this problem in 3 separate discussions.
- Indie fit
- 5.0/10
- Pain
- 6.3/10
- Frequency
- 7.0/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Professionals
- Competition
- Medium
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
it solves this software not having the basic functionality to run something after the sync is done. If you want a proper hook, you can wait, I can't as i'm probably go extinct before it appears if it even does. It has no other issue on Linux, you just wrap it as a systemd service
Previously I was using custom inotify scripts but they were unefficient and/or unreliable. So I wrote a simple daemon to react to Syncthing events using the REST API, and run configurable commands: stfed
Build brief
See what to build and who will buy it
- 1 product idea with the smallest useful version and pricing
- 5 places to find your first customers
- 4 more quotes from people who have this problem
- Current workarounds, existing solutions and risks