doc/packaging: clarify and expand
This commit is contained in:
parent
9579998e63
commit
f2b6d0864b
@ -2,7 +2,7 @@
|
|||||||
|
|
||||||
## Building
|
## Building
|
||||||
|
|
||||||
Using the `Makefile` is recommended. The `GOFLAGS` variable can be used to
|
Using `make` is recommended for building. The `GOFLAGS` variable can be used to
|
||||||
customize flags passed to Go. In particular, `GOFLAGS="-tags=libsqlite3"` can
|
customize flags passed to Go. In particular, `GOFLAGS="-tags=libsqlite3"` can
|
||||||
be used to link to the system's libsqlite3.
|
be used to link to the system's libsqlite3.
|
||||||
|
|
||||||
@ -18,9 +18,13 @@ config file and the admin Unix socket. These can be customized via the
|
|||||||
- Uses a filesystem message store in `/var/lib/soju/logs/`.
|
- Uses a filesystem message store in `/var/lib/soju/logs/`.
|
||||||
- Enables the admin Unix socket (required for `sojuctl`).
|
- Enables the admin Unix socket (required for `sojuctl`).
|
||||||
|
|
||||||
|
The default configuration file's template is stored in `config.in`.
|
||||||
|
|
||||||
## Service manager integration
|
## Service manager integration
|
||||||
|
|
||||||
soju is designed to be run as a system-wide service under a separate user
|
soju is designed to be run as a system-wide service under a separate user
|
||||||
account.
|
account.
|
||||||
|
|
||||||
SIGHUP can be sent to soju to reload the configuration file.
|
SIGHUP can be sent to soju to reload the configuration file.
|
||||||
|
|
||||||
|
A template for systemd is available in `contrib/soju.service`.
|
||||||
|
Loading…
Reference in New Issue
Block a user