commit 6d3cebf9f47127c0a0fbc1a9f2a0413dae59685f
Author: Wim <wim@42.be>
Date: Sat Oct 29 17:34:27 2016 +0000
Update documentation
diff --git a/matterbridge.toml.sample b/matterbridge.toml.sample
index 4e478f8..90a2130 100644
--- a/matterbridge.toml.sample
+++ b/matterbridge.toml.sample
@@ -3058 +3058 @@ RemoteNickFormat="[{PROTOCOL}] <{NICK}> "
#
#Most of the time [[gateway.in]] and [[gateway.out]] are the same if you
#want bidirectional bridging.
+#
-#REQUIRED
[[gateway]]
#OPTIONAL (not used for now)
name="gateway1"
@@ -3306 +3308 @@ enable=true
#xmpp - channel
#slack - channel (the channel name as seen in the URL, not the displayname)
#discord - channel (without the #)
+ # - ID:123456789 (where 123456789 is the channel ID)
+ # (https://github.com/42wim/matterbridge/issues/57)
#REQUIRED
channel="#testing"
@@ -3443 +34614 @@ enable=true
[[gateway.out]]
account="mattermost.work"
channel="off-topic"
+
+
+#If you want to do a 1:1 mapping between protocols where the channelnames are the same
+#e.g. slack and mattermost you can use the samechannelgateway configuration
+#the example configuration below send messages from channel testing on mattermost to
+#channel testing on slack and vice versa. (and for the channel testing2 and testing3)
+
+[[samechannelgateway]]
+ enable = false
+ accounts = [ "mattermost.work","slack.hobby" ]
+ channels = [ "testing","testing2","testing3"]
