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
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
|
# Getting started
## Server side
Start by installing soju via your distribution's [package manager]. A container
image is published as [`codeberg.org/emersion/soju`]. Alternatively, you can
compile it from source (see the [README]).
soju's configuration file (located at `/etc/soju/config`) needs to be adjusted
to enable TLS. This can be done in several ways:
- By setting up a reverse proxy which takes care of terminating TLS
connections, and configuring soju to listen on local unencrypted connections
on port 6667:
listen irc://localhost
- By specifying the path to the TLS certificate in the soju configuration file:
tls <cert> <key>
The certificate must be readable by soju, and soju needs to be reloaded when
the certificate is renewed.
Some [user-contributed guides] are available for popular reverse proxies and
TLS certificate tools.
Next, create an initial user:
sojudb create-user <soju username> -admin
Once TLS is set up and an initial user has been created, soju can be started
(e.g. via systemd or another supervisor daemon).
If you're migrating from ZNC, a tool is available to import users, networks and
channels from a ZNC config file:
go run ./contrib/znc-import <znc config file>
## Client side
### Client supporting `soju.im/bouncer-networks`
If you are using a client supporting the `soju.im/bouncer-networks` IRC
extension (see the [client list]), then you can just connect to soju with your
username and password.
If your client doesn't provide a UI to manage IRC networks, you can talk to
`BouncerServ`. See the [man page] or use `/msg BouncerServ help`.
### Other clients
You will need to setup one separate server in your client for each server you
want soju to connect to.
The easiest way to get started is to specify the IRC server address directly in
the username in the client configuration. For example to connect to Libera Chat,
your username will be: `<soju username>/irc.libera.chat`. Also set your soju
password in the password field of your client configuration.
This will autoconfigure soju by adding a network with the address
`irc.libera.chat` and then autoconnect to it. You will now be able to join
any channel like you would normally do.
For more advanced configuration options, you can talk to `BouncerServ`. See the
[man page] or use `/msg BouncerServ help`.
If you intend to connect to the bouncer from multiple clients, you will need to
append a client name in your username. For instance, to connect from a laptop
and a workstation, you can setup each client to use the respective usernames
`<soju username>/irc.libera.chat@laptop` and
`<soju username>/irc.libera.chat@workstation`.
[package manager]: https://repology.org/project/soju/versions
[`codeberg.org/emersion/soju`]: https://codeberg.org/emersion/-/packages/container/soju/latest
[README]: ../README.md
[user-contributed guides]: ../contrib/README.md
[man page]: https://soju.im/doc/soju.1.html#IRC_SERVICE
[client list]: ../contrib/clients.md
|
