1 | soju(1)
|
---|
2 |
|
---|
3 | # NAME
|
---|
4 |
|
---|
5 | soju - IRC bouncer
|
---|
6 |
|
---|
7 | # SYNOPSIS
|
---|
8 |
|
---|
9 | *soju* [options...]
|
---|
10 |
|
---|
11 | # DESCRIPTION
|
---|
12 |
|
---|
13 | soju is a user-friendly IRC bouncer. It connects to upstream IRC servers on
|
---|
14 | behalf of the user to provide extra features.
|
---|
15 |
|
---|
16 | - Multiple separate users sharing the same bouncer, each with their own
|
---|
17 | upstream servers
|
---|
18 | - Clients connecting to multiple upstream servers via a single connection to
|
---|
19 | the bouncer
|
---|
20 | - Sending the backlog (messages received while the user was disconnected from
|
---|
21 | the bouncer), with per-client buffers
|
---|
22 |
|
---|
23 | When joining a channel, the channel will be saved and automatically joined on
|
---|
24 | the next connection. When registering or authenticating with NickServ, the
|
---|
25 | credentials will be saved and automatically used on the next connection if the
|
---|
26 | server supports SASL. When parting a channel with the reason "detach", the
|
---|
27 | channel will be detached instead of being left.
|
---|
28 |
|
---|
29 | When all clients are disconnected from the bouncer, the user is automatically
|
---|
30 | marked as away.
|
---|
31 |
|
---|
32 | soju supports two connection modes:
|
---|
33 |
|
---|
34 | - Single upstream mode: one downstream connection maps to one upstream
|
---|
35 | connection. To enable this mode, connect to the bouncer with the username
|
---|
36 | "<username>/<network>". If the bouncer isn't connected to the upstream
|
---|
37 | server, it will get automatically added. Then channels can be joined and
|
---|
38 | parted as if you were directly connected to the upstream server.
|
---|
39 | - Multiple upstream mode: one downstream connection maps to multiple upstream
|
---|
40 | connections. Channels and nicks are suffixed with the network name. To join
|
---|
41 | a channel, you need to use the suffix too: _/join #channel/network_. Same
|
---|
42 | applies to messages sent to users.
|
---|
43 |
|
---|
44 | For per-client history to work, clients need to indicate their name. This can
|
---|
45 | be done by adding a "@<client>" suffix to the username.
|
---|
46 |
|
---|
47 | # OPTIONS
|
---|
48 |
|
---|
49 | *-h, -help*
|
---|
50 | Show help message and quit.
|
---|
51 |
|
---|
52 | *-config* <path>
|
---|
53 | Path to the config file. If unset, a default config file is used.
|
---|
54 |
|
---|
55 | *-debug*
|
---|
56 | Enable debug logging (this will leak sensitive information such as
|
---|
57 | passwords).
|
---|
58 |
|
---|
59 | *-listen* <address>
|
---|
60 | Listening address (default: ":6667").
|
---|
61 |
|
---|
62 | # CONFIG FILE
|
---|
63 |
|
---|
64 | The config file has one directive per line.
|
---|
65 |
|
---|
66 | *listen* <address>
|
---|
67 | Listening address (default: ":6667").
|
---|
68 |
|
---|
69 | *hostname* <name>
|
---|
70 | Server hostname (default: system hostname).
|
---|
71 |
|
---|
72 | *tls* <cert> <key>
|
---|
73 | Enable TLS support. The certificate and the key files must be PEM-encoded.
|
---|
74 |
|
---|
75 | *sql* <driver> <source>
|
---|
76 | Set the SQL driver settings. The only supported driver is "sqlite3". The
|
---|
77 | source is the path to the SQLite database file. By default, the path to the
|
---|
78 | database file is "soju.db".
|
---|
79 |
|
---|
80 | *log* <path>
|
---|
81 | Path to the bouncer logs root directory, or empty to disable logging. By
|
---|
82 | default, logging is disabled.
|
---|
83 |
|
---|
84 | # IRC SERVICE
|
---|
85 |
|
---|
86 | soju exposes an IRC service called *BouncerServ* to manage the bouncer.
|
---|
87 | Commands can be sent via regular private messages
|
---|
88 | (_/msg BouncerServ <command> [args...]_). Commands may be written in full or
|
---|
89 | abbreviated form, for instance *network* can be abbreviated as *net* or just
|
---|
90 | *n*.
|
---|
91 |
|
---|
92 | *help* [command]
|
---|
93 | Show a list of commands. If _command_ is specified, show a help message for
|
---|
94 | the command.
|
---|
95 |
|
---|
96 | *network create* *-addr* <addr> [options...]
|
---|
97 | Connect to a new network at _addr_. _-addr_ is mandatory.
|
---|
98 |
|
---|
99 | _addr_ supports several connection types:
|
---|
100 | - _[ircs://]host[:port]_ connects with TLS over TCP
|
---|
101 | - _irc+insecure://host[:port]_ connects with plain-text TCP
|
---|
102 |
|
---|
103 | Other options are:
|
---|
104 |
|
---|
105 | *-name* <name>
|
---|
106 | Short network name. This will be used instead of _addr_ to refer to the
|
---|
107 | network.
|
---|
108 |
|
---|
109 | *-username* <username>
|
---|
110 | Connect with the specified username. By default, the nickname is used.
|
---|
111 |
|
---|
112 | *-pass* <pass>
|
---|
113 | Connect with the specified server password.
|
---|
114 |
|
---|
115 | *-realname* <realname>
|
---|
116 | Connect with the specified real name. By default, the nickname is used.
|
---|
117 |
|
---|
118 | *-nick* <nickname>
|
---|
119 | Connect with the specified nickname. By default, the account's username
|
---|
120 | is used.
|
---|
121 |
|
---|
122 | *network delete* <name>
|
---|
123 | Disconnect and delete a network.
|
---|
124 |
|
---|
125 | *network status*
|
---|
126 | Show a list of saved networks and their current status.
|
---|
127 |
|
---|
128 | # AUTHORS
|
---|
129 |
|
---|
130 | Maintained by Simon Ser <contact@emersion.fr>, who is assisted by other
|
---|
131 | open-source contributors. For more information about soju development, see
|
---|
132 | https://git.sr.ht/~emersion/soju.
|
---|