Notification service

hbons edited this page Jul 18, 2012 · 12 revisions

Notification Service

SparkleShare uses a small script that handles update notifications between clients. By default it uses the one running on The only information sent to this service is a hash of a folder identifier and a hash of the current revision. The service then tells the other connected clients that are subscribed to a folder that they can pull new changes from wherever your repository is hosted. This allows SparkleShare clients to sync new changes instantly, instead of polling with potentially long delays (up to 10 minutes).

Running your own

Having a centralised service to handle notifications is needed for a pleasant user experience. If you do feel uncomfortable with this you are able to run your own. Just run on your own server and edit the SparkleShare configuration (in ~/.config/sparkleshare/config.xml) to point to it:

  // Use your personal notification service globally...
  // ...or for a single folder

Git hook

There's a git hook that allows you to do manual pushes to the repo, and the SparkleShare clients will still pick it up:

You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Press h to open a hovercard with more details.