Improve config.example.ini

This commit is contained in:
Drew DeVault 2019-12-19 11:05:48 -05:00
parent fbc03ed029
commit c93b55384d
1 changed files with 20 additions and 13 deletions

View File

@ -16,17 +16,21 @@ owner-email=sir@cmpwn.com
# The source code for your fork of sr.ht # The source code for your fork of sr.ht
source-url=https://git.sr.ht/~sircmpwn/srht source-url=https://git.sr.ht/~sircmpwn/srht
# #
# A secret key to encrypt session cookies with. Use `srht-keygen service` to # A key used for encrypting session cookies. Use `srht-keygen service` to
# generate this. This should be unique to each site, but shared among nodes of # generate the service key. This must be shared between each node of the same
# that site. For example, git.sr.ht and hg.sr.ht have different keys, but # service (e.g. git1.sr.ht and git2.sr.ht), but different services may use
# git1.sr.ht has the same key as git2.sr.ht. # different keys. If you configure all of your services with the same
# config.ini, you may use the same service-key for all of them.
service-key= service-key=
# #
# A secret key to encrypt internal messages with. Use `srht-keygen network` to # A secret key to encrypt internal messages with. Use `srht-keygen network` to
# generate this. This should be consistent between all *.sr.ht sites and nodes. # generate this key. It must be consistent between all services and nodes.
network-key= network-key=
# #
# The redis host url. # The redis host URL. This is used for caching and temporary storage, and must
# be shared between nodes (e.g. git1.sr.ht and git2.sr.ht), but need not be
# shared between services. It may be shared between services, however, with no
# ill effect, if this better suits your infrastructure.
redis-host= redis-host=
[mail] [mail]
@ -42,10 +46,12 @@ smtp-from=
error-to= error-to=
error-from= error-from=
# #
# Your PGP key information (DO NOT mix up pub and priv here) # You should generate a PGP key to allow users to authenticate emails received
# You must remove the password from your secret key, if present. # from your services. Use `gpg --edit-key [key id]` to remove the password from
# You can do this with gpg --edit-key [key-id], then use the passwd # your private key, then export it to a file and set pgp-privkey to the path to
# command and do not enter a new password. # that file. pgp-pubkey should be set to the path to your public key, and
# pgp-key-id should be set to the key ID string. Outgoing emails are signed with
# this PGP key.
pgp-privkey= pgp-privkey=
pgp-pubkey= pgp-pubkey=
pgp-key-id= pgp-key-id=
@ -53,10 +59,11 @@ pgp-key-id=
[webhooks] [webhooks]
# #
# base64-encoded Ed25519 key for signing webhook payloads. This should be # base64-encoded Ed25519 key for signing webhook payloads. This should be
# consistent for all *.sr.ht sites, as we'll use this key to verify signatures # consistent between all services.
# from other sites in your network.
# #
# Use the srht-webhook-keygen command to generate a key. # Use the `srht-keygen webhook` command to generate this key. Put the private
# key here and distribute the public key to anyone who would want to verify
# webhook payloads from your service.
private-key= private-key=
[man.sr.ht] [man.sr.ht]