Triggered web site rebuilds and similar

Right now to rebuild web-sites for from version control we
have a setup that looks something like:

 - we send mail to a user on an a different machine
 - in the procmailrc for that user we touch a file
 - in a cron job we notice that the file has changed and perform
   the rebuild

That's pretty horrible. A little while ago I sat down over an evening
or two and created a simple daemon/client pair called 'fishpoll'. It
basically works like this:

 A) On you install fishpolld and a script


 B) In your commit hook, you do:

     fishpollc rebuild_gnome_web

(You'd probably actually do it over the back-channel network, not the
public network, simplifying above.) That talks to fishpolld on the
other machine and tells it to run the script at the next opportunity.
It will never run the same handler twice at the same time so its

There's more details at:
  git clone git://

I'm thinking of deploying this on, at least for a few things,
but have some feeling I'm probably reinventing the wheel badly. It's an
obvious problem, there must be a better standard answer... or is there?

Suggestions appreciated.

- Owen

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]