Updated documentation.

This commit is contained in:
default 2023-10-22 17:49:03 +02:00
parent 7a71046b61
commit 71225fc271

View file

@ -395,15 +395,30 @@ credentials defined for this user. Search people, start following
them, engage in arid discussions and generally enjoy the frustrating them, engage in arid discussions and generally enjoy the frustrating
experience of Social Media. experience of Social Media.
.Pp .Pp
The following example configures OpenBSD's httpd as a frontend using the Since version 2.43,
FastCGI interface. There is no need to use relayd, as httpd includes
native FastCGI support (please take note that you must reconfigure
.Nm .Nm
by setting the fastcgi value to true in the supports communicating from / to the front end http server using the FastCGI
.Pa server.json protocol. There is no special advantage in using this, only that some servers
configuration file). Add the following to the example.com server section in allow for simpler configuration. For example, in the case of nginx, you can
.Pa /etc/httpd.conf : replace the two 'proxy_pass' and 'proxy_set_header' lines in the example
above with just
.Bd -literal -offset indent .Bd -literal -offset indent
fastcgi_pass localhost:8001;
.Ed
.Pp
The only thing to change on
.Nm
size is to the set 'fastcgi' value to true in
.Pa server.json .
.Pp
Further, using the FastCGI interface allows a much simpler configuration
under OpenBSD's native httpd, given that it's natively implemented there
and you no longer need to configure the complicated relayd server. This is
an example:
.Bd -literal -offset indent
# other server configuration
[...]
location "/fedi*" { location "/fedi*" {
fastcgi socket tcp "127.0.0.1" 8001 fastcgi socket tcp "127.0.0.1" 8001
} }