This repository was archived by the owner on Jun 24, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 8
/
Copy pathrocketchat.example.conf
49 lines (43 loc) · 1.74 KB
/
rocketchat.example.conf
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
# vim: syntax=yaml
# Example configuration for bridging XMPP with RocketChat.
#
# The <placeholders> need to be filled out.
#
# This would connect to the XMPP MUC "conference1" using the account
# "alice" and relay messages to and from this MUC to a RocketChat-instance,
# as specified by the webhooks. The webhooks need to be configured in
# RocketChat aswell.
#
# Refer to the CONFIGURATION.rst for detailed documentation of all settings.
xmpp:
jid: <[email protected]>
password: "<bot-password>"
# A list of all MUCs that should be available to the bridges defined later.
mucs:
- jid: <[email protected]>
nickname: <nickname>
# password: "<muc-password>"
incoming_webhook_listener:
# The outgoing webhook URL that must be set in Rocket.Chat is of the form
# "http://{bind_adress}:{port}/".
bind_address: "127.0.0.1"
port: 5000
bridges:
- xmpp_endpoints:
- muc: <[email protected]>
outgoing_webhooks:
# Note: "Outgoing from this bridge" means "Incoming to RocketChat",
# so this URL refers to the incoming webhook URL of RocketChat.
- url: <incoming-webhook-url-from-rocketchat>
override_username: "{nick}"
incoming_webhooks:
# Note: "Incoming to this bridge" means "Outgoing from RocketChat",
# so this token must match the token in the outgoing webhook from
# RocketChat.
- token: <outgoing-webhook-token-from-rocketchat>
ignore_user:
# This ignores incoming messages from the default Rocket.Chat bot.
# This should be replaced with the user that is set in the
# incoming integration in Rocket.Chat so that messages from this
# bridge are not duplicated back to XMPP.
- "rocket.cat"