debian-mirror-gitlab/doc/user/project/integrations/irker.md

61 lines
2.6 KiB
Markdown
Raw Normal View History

2020-10-24 23:57:45 +05:30
---
stage: Create
group: Ecosystem
2021-02-22 17:27:13 +05:30
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
2020-10-24 23:57:45 +05:30
---
2021-04-17 20:07:23 +05:30
# Irker IRC Gateway **(FREE)**
2017-08-17 22:00:37 +05:30
GitLab provides a way to push update messages to an Irker server. When
2021-02-22 17:27:13 +05:30
configured, pushes to a project trigger the service to send data directly
2017-08-17 22:00:37 +05:30
to the Irker server.
2021-03-11 19:13:27 +05:30
See the [project homepage](https://gitlab.com/esr/irker) for further information.
2017-08-17 22:00:37 +05:30
## Needed setup
2021-02-22 17:27:13 +05:30
You first need an Irker daemon. You can download the Irker code
2021-01-03 14:25:43 +05:30
[from its repository](https://gitlab.com/esr/irker):
2017-08-17 22:00:37 +05:30
2020-04-08 14:13:33 +05:30
```shell
2017-08-17 22:00:37 +05:30
git clone https://gitlab.com/esr/irker.git
```
2019-12-21 20:55:43 +05:30
Once you have downloaded the code, you can run the Python script named `irkerd`.
2017-08-17 22:00:37 +05:30
This script is the gateway script, it acts both as an IRC client, for sending
messages to an IRC server obviously, and as a TCP server, for receiving messages
from the GitLab service.
2021-02-22 17:27:13 +05:30
If the Irker server runs on the same machine, you are done. If not, you
need to follow the first steps of the next section.
2017-08-17 22:00:37 +05:30
## Complete these steps in GitLab
1. Navigate to the project you want to configure for notifications.
2020-04-22 19:07:51 +05:30
1. Navigate to the [Integrations page](overview.md#accessing-integrations)
2017-08-17 22:00:37 +05:30
1. Click "Irker".
2020-04-22 19:07:51 +05:30
1. Ensure that the **Active** toggle is enabled.
2017-08-17 22:00:37 +05:30
1. Enter the server host address where `irkerd` runs (defaults to `localhost`)
2019-07-07 11:18:12 +05:30
in the `Server host` field on the Web page
2017-08-17 22:00:37 +05:30
1. Enter the server port of `irkerd` (e.g. defaults to 6659) in the
2019-07-07 11:18:12 +05:30
`Server port` field on the Web page.
2017-08-17 22:00:37 +05:30
1. Optional: if `Default IRC URI` is set, it has to be in the format
2021-02-22 17:27:13 +05:30
`irc[s]://domain.name` and is prepended to each and every channel provided
2019-07-07 11:18:12 +05:30
by the user which is not a full URI.
2017-08-17 22:00:37 +05:30
1. Specify the recipients (e.g. #channel1, user1, etc.)
1. Save or optionally click "Test Settings".
## Note on Irker recipients
Irker accepts channel names of the form `chan` and `#chan`, both for the
2021-02-22 17:27:13 +05:30
`#chan` channel. If you want to send messages in query, you need to add
2017-08-17 22:00:37 +05:30
`,isnick` after the channel name, in this form: `Aorimn,isnick`. In this latter
case, `Aorimn` is treated as a nick and no more as a channel name.
Irker can also join password-protected channels. Users need to append
2020-11-24 15:15:51 +05:30
`?key=thesecretpassword` to the channel name. When using this feature remember to
2021-02-22 17:27:13 +05:30
**not** put the `#` sign in front of the channel name; failing to do so
results in Irker joining a channel literally named `#chan?key=password` henceforth
2018-03-17 18:26:18 +05:30
leaking the channel key through the `/whois` IRC command (depending on IRC server
2021-01-03 14:25:43 +05:30
configuration). This is due to a long standing Irker bug.