starred/audiobookshelf
1
0
Fork 0
mirror of https://github.com/advplyr/audiobookshelf.git synced 2026-05-30 23:40:40 +02:00
Code Issues 1.0k Packages Projects Releases 10 Wiki Activity

[PR #2489] [CLOSED] Allow user to override log level #3727

New Issue
Closed
opened 2026-04-25 00:16:49 +02:00 by adam · 0 comments
adam commented 2026-04-25 00:16:49 +02:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/advplyr/audiobookshelf/pull/2489
Author: @FreedomBen
Created: 1/3/2024
Status: ❌ Closed

Base: master ← Head: more-logging-settings

📝 Commits (1)

  • b1dd88f Allow user to override log level

📊 Changes

2 files changed (+34 additions, -4 deletions)

View changed files

📝 server/Logger.js (+11 -2)
📝 server/utils/constants.js (+23 -2)

📄 Description

This PR adds an environment variable LOG_LEVEL that can be used to control the application log level. For example, this would allow you to view dev logs while in production, should you so choose.

If the env var is not set, behavior should not change from the current behavior.

Env var can be set with the log level string (case insensitive). For example: LOG_LEVEL=debug

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/advplyr/audiobookshelf/pull/2489 **Author:** [@FreedomBen](https://github.com/FreedomBen) **Created:** 1/3/2024 **Status:** ❌ Closed **Base:** `master` ← **Head:** `more-logging-settings` --- ### 📝 Commits (1) - [`b1dd88f`](https://github.com/advplyr/audiobookshelf/commit/b1dd88f33f1da3fd7fe2a1d933036ad95a00f884) Allow user to override log level ### 📊 Changes **2 files changed** (+34 additions, -4 deletions) <details> <summary>View changed files</summary> 📝 `server/Logger.js` (+11 -2) 📝 `server/utils/constants.js` (+23 -2) </details> ### 📄 Description This PR adds an environment variable `LOG_LEVEL` that can be used to control the application log level. For example, this would allow you to view dev logs while in production, should you so choose. If the env var is not set, behavior should not change from the current behavior. Env var can be set with the log level string (case insensitive). For example: `LOG_LEVEL=debug` --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
adam added the pull-request label 2026-04-25 00:16:49 +02:00
adam closed this issue 2026-04-25 00:16:49 +02:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
authentication
backlog
bug
chapter editor
config-issue
ebooks
encoding/embedding
enhancement
help wanted
listening sessions & progress
planned
possible plugin
progress sync
pull-request
Mirrored from GitHub Pull Request
 sorting/filtering/searching
unable to reproduce
upload
users & permissions
waiting
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam (Adam Melkus)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/audiobookshelf#3727
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?