Skip to content

Conversation

@remsky
Copy link
Owner

@remsky remsky commented Nov 5, 2025

This PR adds support for configuring the global API logging level via the
API_LOG_LEVEL environment variable, allowing users to control log verbosity
without code changes.

Changes:

  • Added API_LOG_LEVEL environment variable support in main.py
  • Validates against loguru's valid levels (TRACE, DEBUG, INFO, SUCCESS, WARNING, ERROR, CRITICAL)
  • Defaults to DEBUG to maintain backward compatibility
  • Updated docker-compose.yml files for both CPU and GPU with explicit API_LOG_LEVEL=DEBUG
  • Added comprehensive documentation in README with examples for Docker, Linux/macOS, and Windows

Benefits:

  • Production deployments can reduce log noise by setting to WARNING or ERROR
  • Development environments can increase verbosity with TRACE
  • No code changes required - purely configuration-driven
  • Fully backward compatible - maintains current DEBUG default

Reviewed and merged from PR #404.

…le support

This PR adds support for configuring the global API logging level via the
API_LOG_LEVEL environment variable, allowing users to control log verbosity
without code changes.

Changes:
- Added API_LOG_LEVEL environment variable support in main.py
- Validates against loguru's valid levels (TRACE, DEBUG, INFO, SUCCESS, WARNING, ERROR, CRITICAL)
- Defaults to DEBUG to maintain backward compatibility
- Updated docker-compose.yml files for both CPU and GPU with explicit API_LOG_LEVEL=DEBUG
- Added comprehensive documentation in README with examples for Docker, Linux/macOS, and Windows

Benefits:
- Production deployments can reduce log noise by setting to WARNING or ERROR
- Development environments can increase verbosity with TRACE
- No code changes required - purely configuration-driven
- Fully backward compatible - maintains current DEBUG default

Reviewed and merged from PR #404.
@remsky remsky closed this Nov 5, 2025
@remsky remsky deleted the claude/review-backlog-prs-011CUp2MXLh8QihoaD3ZnXF5 branch November 27, 2025 01:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants