Shiloh/githaven
Shiloh/githaven
1
0
Fork 1
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

Fix typo for LOG_COMPRESSION in ini (#31809)

Browse Source 
Follow #31761

---------

Co-authored-by: silverwind <me@silverwind.io>
This commit is contained in:
Jason Song 2024-08-10 06:07:35 +08:00 committed by GitHub
parent fb271d1e6a
commit 42841aab59
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
custom/conf/app.example.ini
View File

@ -2688,7 +2688,7 @@ LEVEL = Info
;; Logs retention time in days. Old logs will be deleted after this period. ;; Logs retention time in days. Old logs will be deleted after this period.
;LOG_RETENTION_DAYS = 365 ;LOG_RETENTION_DAYS = 365
;; Log compression type, `none` for no compression, `zstd` for zstd compression. ;; Log compression type, `none` for no compression, `zstd` for zstd compression.
;; Other compression types like `gzip` if NOT supported, since seekable stream is required for log view. ;; Other compression types like `gzip` are NOT supported, since seekable stream is required for log view.
;; It's always recommended to use compression when using local disk as log storage if CPU or memory is not a bottleneck. ;; It's always recommended to use compression when using local disk as log storage if CPU or memory is not a bottleneck.
;; And for object storage services like S3, which is billed for requests, it would cause extra 2 times of get requests for each log view. ;; And for object storage services like S3, which is billed for requests, it would cause extra 2 times of get requests for each log view.
;; But it will save storage space and network bandwidth, so it's still recommended to use compression. ;; But it will save storage space and network bandwidth, so it's still recommended to use compression.