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.
|
---|
27 |
|
---|
28 | soju supports two connection modes:
|
---|
29 |
|
---|
30 | - Single upstream mode: one downstream connection maps to one upstream
|
---|
31 | connection. To enable this mode, connect to the bouncer with the username
|
---|
32 | "<username>/<network>". If the bouncer isn't connected to the upstream
|
---|
33 | server, it will get automatically added. Then channels can be joined and
|
---|
34 | parted as if you were directly connected to the upstream server.
|
---|
35 | - Multiple upstream mode: one downstream connection maps to multiple upstream
|
---|
36 | connections. Channels and nicks are suffixed with the network name. To join
|
---|
37 | a channel, you need to use the suffix too: _/join #channel/network_. Same
|
---|
38 | applies to messages sent to users.
|
---|
39 |
|
---|
40 | # OPTIONS
|
---|
41 |
|
---|
42 | *-h, -help*
|
---|
43 | Show help message and quit.
|
---|
44 |
|
---|
45 | *-config* <path>
|
---|
46 | Path to the config file.
|
---|
47 |
|
---|
48 | *-debug*
|
---|
49 | Enable debug logging (this will leak sensitive information such as
|
---|
50 | passwords).
|
---|
51 |
|
---|
52 | *-listen* <address>
|
---|
53 | Listening address (default: ":6667").
|
---|
54 |
|
---|
55 | # CONFIG FILE
|
---|
56 |
|
---|
57 | The config file has one directive per line.
|
---|
58 |
|
---|
59 | *listen* <address>
|
---|
60 | Listening address (default: ":6667").
|
---|
61 |
|
---|
62 | *hostname* <name>
|
---|
63 | Server hostname (default: system hostname).
|
---|
64 |
|
---|
65 | *tls* <cert> <key>
|
---|
66 | Enable TLS support. The certificate and the key files must be PEM-encoded.
|
---|
67 |
|
---|
68 | *sql* <driver> <source>
|
---|
69 | Set the SQL driver settings. The only supported driver is "sqlite". The
|
---|
70 | source is the path to the SQLite database file.
|
---|
71 |
|
---|
72 | # IRC SERVICE
|
---|
73 |
|
---|
74 | soju exposes an IRC service called BouncerServ to manage the bouncer. Commands
|
---|
75 | can be sent via regular private messages (_/msg BouncerServ <command> [args...]_).
|
---|
76 |
|
---|
77 | *help* [command]
|
---|
78 | Show a list of commands. If _command_ is specified, show a help message for
|
---|
79 | the command.
|
---|
80 |
|
---|
81 | *create-network* *-addr* <addr> [options...]
|
---|
82 | Connect to a new network at _addr_. _-addr_ is mandatory. Other options are:
|
---|
83 |
|
---|
84 | *-name* <name>
|
---|
85 | Short network name. This will be used instead of _addr_ to refer to the
|
---|
86 | network.
|
---|
87 |
|
---|
88 | *-username* <username>
|
---|
89 | Connect with the specified username. By default, the nickname is used.
|
---|
90 |
|
---|
91 | *-pass* <pass>
|
---|
92 | Connect with the specified server password.
|
---|
93 |
|
---|
94 | *-realname* <realname>
|
---|
95 | Connect with the specified real name. By default, the nickname is used.
|
---|
96 |
|
---|
97 | *-nick* <nickname>
|
---|
98 | Connect with the specified nickname. By default, the account's username
|
---|
99 | is used.
|
---|
100 |
|
---|
101 | # AUTHORS
|
---|
102 |
|
---|
103 | Maintained by Simon Ser <contact@emersion.fr>, who is assisted by other
|
---|
104 | open-source contributors. For more information about mako development, see
|
---|
105 | https://git.sr.ht/~emersion/soju.
|
---|