GitHub/ergo
3
0
Fork 0
mirror of https://github.com/ergochat/ergo.git synced 2026-01-29 13:37:55 +01:00
Code Issues Projects Releases Wiki Activity

clarify when history.channel-length applies (#2323)

Browse Source
This commit is contained in:
Shivaram Lingamneni 2026-01-27 08:13:21 -08:00 committed by GitHub
parent 3ff0341944
commit 2b1dad982f
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 8 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
default.yaml
View File

@ -1007,10 +1007,12 @@ history:
# in your country and the countries of your users.
enabled: true
# how many channel-specific events (messages, joins, parts) should be tracked per channel?
# if the in-memory backend is enabled for a channel, how many channel-specific events
# (messages, joins, parts) should be retained?
channel-length: 2048
# how many direct messages and notices should be tracked per user?
# if the in-memory backend is enabled for a user, how many direct messages
# and notices should be retained?
client-length: 256
# how long should we try to preserve messages?

6
traditional.yaml
View File

@ -978,10 +978,12 @@ history:
# in your country and the countries of your users.
enabled: true
# how many channel-specific events (messages, joins, parts) should be tracked per channel?
# if the in-memory backend is enabled for a channel, how many channel-specific events
# (messages, joins, parts) should be retained?
channel-length: 2048
# how many direct messages and notices should be tracked per user?
# if the in-memory backend is enabled for a user, how many direct messages
# and notices should be retained?
client-length: 256
# how long should we try to preserve messages?