Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
I
irker
Manage
Activity
Members
Labels
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Locked files
Deploy
Releases
Package Registry
Model registry
Operate
Terraform modules
Analyze
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
iDB
irker
Commits
1e1b5429
Commit
1e1b5429
authored
12 years ago
by
Eric S. Raymond
Browse files
Options
Downloads
Patches
Plain Diff
More about testing.
parent
ff02cb2b
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
install.txt
+8
-4
8 additions, 4 deletions
install.txt
with
8 additions
and
4 deletions
install.txt
+
8
−
4
View file @
1e1b5429
...
...
@@ -16,7 +16,7 @@ humans watching irkerd's output, are mere spam).
See the security.txt document for a detailed discussion of security
and DoS vulnerabilities related to irker.
== Installing irker ==
== Installing irker
d
==
irker needs to run constantly, watching for TCP and UDP traffic on
port 6659. Install it accordingly.
...
...
@@ -46,6 +46,10 @@ ways to install it. See the irkerhook manual page for details.
== Testing ==
Go to a project repo and call irkerhook.py as indicated above while
watching the freenode #commits channel.
To verify that your repo produces well-formed JSON notifications,
you can run irkerhook.py in the repo directory using the -n switch,
which emits JSON to standard output rather than attempting to ship
to an irkerd instance.
Then, start irkerd and call irkerhook.py while watching the freenode
#commits channel.
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment