soju/contrib
Дамјан Георгиевски e510cef208 add an example systemd service file
The service file will run `/usr/bin/soju --config /etc/soju/config`.

By default it'll run as a dynamically created `soju` user and group (DynamicUser=yes),
and it will run in a constrained environment[1], only having write access to
/var/lib/soju and /run/soju

If the admin creates a static `soju` user and group, those static uid/gid will be used,
with the same service constraints. This can be useful to share the static `soju` group
with other services, so they can access the soju logs and database even
if the service is not running (or before it's running).

The procedure for the initial user and database scaffold still
works normally, when run as `root`:
```
mkdir /var/lib/soju/
sojudb -config /etc/soju/config create-user myname -admin
```
NOTE: systemd will automatically change the ownership of files in /var/lib/soju/ when the service
is started.

`sojuctl` will work for root, or with `sudo -u soju`, just normally.

References:
- [1] https://www.freedesktop.org/software/systemd/man/systemd.exec.html#DynamicUser=
2023-03-20 18:12:31 +01:00
..
migrate-db contrib/migrate-db: new script 2022-07-04 15:50:35 +02:00
migrate-logs msgstore: move ZNC log functions to separate package 2023-02-17 14:35:25 +01:00
znc-import Add a flag to disable users 2023-01-26 18:33:55 +01:00
casemap-logs.sh contrib/casemap-logs.sh: new utility script 2021-03-26 15:31:54 +01:00
clients.md contrib/clients: Warn about Hexchat password limit 2023-01-25 00:06:40 +01:00
soju.service add an example systemd service file 2023-03-20 18:12:31 +01:00