1 = Forge installation instructions =
3 irker and irkerhook.py are intended to be installed on forge sites
4 such as SourceForge, GitHub, Gitorious, Gna, and Savannah. This
5 file explains the theory of operation, how to install the code,
8 == Theory of operation ==
10 irkerhook.py creates JSON notification requests and ships them to
11 irkerd's listener socket. irkerd run as a daemon in order to maintain
12 all the client state required to post multiple notifications while generating
13 minimum of join/leave messages (which, from the point of view of
14 humans watching irkerd's output, are mere spam).
16 See the security.txt document for a detailed discussion of security
17 and DoS vulnerabilities related to irker.
23 1. Python at version 2.6 or later, which has JSON built in
25 2. Python at version no older than 2.4, and a version of the
26 simplejson library installed that it can use. Some newer
27 versions of simplejson discard 2.4 compatibility; 2.0.9
30 == Installing irkerd ==
32 irker needs to run constantly, watching for TCP and UDP traffic on
33 port 6659. Install it accordingly. It has no config file; you can
34 just start it up with no arguments. If you want to see what it's
35 doing, give it command-line options -d 1 for sparse messages and -d 2
36 to show all traffic with IRC servers.
38 You should *not* make irker visible from outside the site firewall, as
39 it can be used to spam IRC channels while masking the source address.
41 The file org.catb.irkerd.plist is a Mac OS/X plist that can be
42 installed to launch irkerd as a boot-time service on that system.
44 == Installing irkerhook.py ==
46 Under git, a call to irkerhook.py should be installed in the update
47 hook script of your repo. Under Subversion, the call goes in your
48 repo's post-commit script. Under Mercurial there are two different
49 ways to install it. See the irkerhook manual page for details; the
50 source is irkerhook.xml in this distribution.
52 Note that if you were using the CIA service and have ciabot.py in your
53 git update script, you can simply replace this
55 /path/to/ciabot.py ${refname} $(git rev-list ${oldhead}..${newhead} | tac)
59 /path/to/irkerhook.py --refname=${refname} $(git rev-list ${oldhead}..${newhead} | tac)
61 SourceForge is a special case: see
63 https://github.com/AI0867/sf-git-irker-pipeline
65 for tools and instructions on how to work around its limitations.
69 To verify that your repo produces well-formed JSON notifications,
70 you can run irkerhook.py in the repo directory using the -n switch,
71 which emits JSON to standard output rather than attempting to ship
72 to an irkerd instance.
74 Then, start irkerd and call irkerhook.py while watching the freenode
77 The 'irk' script is a little test tool that takes two arguments,
78 a channel and a message, and does what you'd expect.
80 If you need help, there's a project chat channel at
82 irc://chat.freenode.net/#irker
84 == Read-only access ==
86 If, for whatever reason, you can't modify the hook scripts in your
87 repository, there is still hope.
89 There's a proxy that takes CIA XML-RPC notifications
90 and passes them to a local irker instance. Find it here:
92 https://github.com/nenolod/irker-cia-proxy
94 There's also a poller daemon that can watch activity in a Subversion
95 repository and ship notifications via an irker instance.
97 https://github.com/shikadilord/irker-svnpoller