This manual describes common options and behavior for
public-inbox network daemons. Network daemons for public-inbox
provide read-only NNTP and HTTP access to public-inboxes. Write
-access to a public-inbox repository will never be required to
-run these.
+access to a public-inbox will never be required to run these.
These daemons are implemented with a common core using
non-blocking sockets and optimized for fairness; even with
These daemons may also utilize multiple pre-forked worker
processes to take advantage of multiple CPUs.
-Native TLS (Transport Layer Security) support is planned.
-
=head1 OPTIONS
=over
to listen on. For example, to listen to TCP connections on
port 119, use: C<-l 0.0.0.0:119>. This may also point to
a Unix socket (C<-l /path/to/http.sock>) for a reverse proxy
-like L<nginx(1)> to use.
+like L<nginx(8)> to use.
May be specified multiple times to allow listening on multiple
sockets.
+This does not need to be specified at all if relying on
+L<systemd.socket(5)> or similar
+
Default: server-dependent unless socket activation is used with
L<systemd(1)> or similar (see L<systemd.socket(5)>).
=head1 SIGNALS
-Most of our signal handling behavior is copied from L<nginx(1)>
+Most of our signal handling behavior is copied from L<nginx(8)>
and/or L<starman(1)>; so it is possible to reuse common scripts
for managing them.
=head1 COPYRIGHT
-Copyright 2013-2018 all contributors L<mailto:meta@public-inbox.org>
+Copyright 2013-2020 all contributors L<mailto:meta@public-inbox.org>
License: AGPL-3.0+ L<https://www.gnu.org/licenses/agpl-3.0.txt>