Script validates input and fails on invalid LOG_LEVEL
Script generates .env.logging with correct mappings
Script is executable (chmod +x)
Script has documentation in header comments
## Summary
- Create `scripts/ci/generate-log-config.sh` that maps a single LOG_LEVEL env var to per-container settings
- Script accepts DEBUG, INFO, WARN, or ERROR and validates input
- Generates `.env.logging` with mappings for Backend/OCR (Pino), Frontend (Vite), PostgreSQL, Redis, and Traefik
- Integrate script into staging and production CI/CD pipelines
- Add `.env.logging` to `.gitignore`
Fixes #81
## Test plan
- [x] Script accepts LOG_LEVEL argument (DEBUG, INFO, WARN, ERROR)
- [x] Script validates input and fails on invalid LOG_LEVEL
- [x] Script generates `.env.logging` with correct mappings per container
- [x] Script is executable and documented in header
## Acceptance Criteria
- [x] Script accepts LOG_LEVEL argument (DEBUG, INFO, WARN, ERROR)
- [x] Script validates input and fails on invalid LOG_LEVEL
- [x] Script generates .env.logging with correct mappings
- [x] Script is executable (chmod +x)
- [x] Script has documentation in header comments
Create generate-log-config.sh that maps a single LOG_LEVEL env var to
per-container settings for Backend, Frontend, PostgreSQL, Redis, and
Traefik. Script validates input and generates .env.logging file.
Integrate script into staging and production CI/CD pipelines.
Remove obsolete SPRINTS.md calendar file.
Co-Authored-By: Claude Opus 4.5 <[email protected]>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
scripts/ci/generate-log-config.shthat maps a single LOG_LEVEL env var to per-container settings.env.loggingwith mappings for Backend/OCR (Pino), Frontend (Vite), PostgreSQL, Redis, and Traefik.env.loggingto.gitignoreFixes #81
Test plan
.env.loggingwith correct mappings per containerAcceptance Criteria