On Thu, Mar 12, 2015 at 5:48 AM, Gour <g...@atmarama.net> wrote: > Ron W <ronw.m...@gmail.com> writes: > > > Another possibility might be RSS. I recall reading on this list where > some > > have set up build servers, such as Jenkins, that monitor the Fossil RSS > > feed. > > I believe that's too complicated considering that atm I'm the only one > generating the content...
While a build server is probably too complicated, a web content updater could be something like: #!/usr/bin/bash $PREVIOUS=/path/to/a/file $CURRENT=/path/to/another/file $INTERVAL=300 # time, in seconds, between checks for available updates while (1) do wget 'http://localhost:8080/timeline.rss?r=trunk&n=1' | grep '<guid>' >$CURRENT cmp -s $PREVIOUS $CURRENT if [ $? -ne 0 ] # might need to be -eq instead of -ne (FYI: These are numeric compare in Bash) then fossil update rsync ./public $WWW/public # only needed if not serving directly from the check-out mv $CURRENT $PREVIOUS fi sleep $INTERVAL od
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
