logo

pleroma

My custom branche(s) on git.pleroma.social/pleroma/pleroma git clone https://anongit.hacktivis.me/git/pleroma.git/
commit: 427db326032628248b44439d5593f8395b3de428
parent 9b39065595ee49dad929c2613bf5ec04413039a7
Author: Phantasm <phantasm@centrum.cz>
Date:   Tue, 12 Nov 2024 00:21:33 +0100

openbsd relayd: clarify certificate naming

Diffstat:

Minstallation/openbsd/relayd.conf4++--
1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/installation/openbsd/relayd.conf b/installation/openbsd/relayd.conf @@ -16,7 +16,7 @@ ext_inet="<ipaddr>" table <pleroma_server> { 127.0.0.1 } -# Uncomment next line when you want to serve other services than Pleroma. +# Uncomment when you want to serve other services than Pleroma. # In this example tables are used only as way to differentiate between Pleroma and other services. # Feel free to rename "httpd_server" everywhere to fit your setup. #table <httpd_server> { 127.0.0.1 } @@ -30,7 +30,7 @@ http protocol pleroma { # Protocol for upstream Pleroma server # When serving multiple services with different certificates, specify multiple "tls keypair" keywords # and add forwards to those services before the block keyword near the bottom of the protocol and relay configurations. - # The string in quotes must match the fullchain certificate file create by acme-client. + # The string in quotes must match the fullchain certificate file created by acme-client without the extension. # For example: # tls keypair "pleroma.example.tld" # tls keypair "example.tld"