- Updated README.md with Telegram features section in 'Latest Features'
- Added Telegram environment variables to Environment Variables table
- Updated FEATURE_PLAN-telegram.md: marked Phases 1-5 as completed
- Updated status table with completion dates (Phase 1-4: done, Phase 5: docs complete)
OpenAPI Documentation:
- Added swagger tags to reorder route (Management Portal)
- Added swagger tags to consent routes (Consent Management)
- Regenerated openapi.json with correct tags (no more 'default' category)
Environment Configuration:
- Updated .env.backend.example with Telegram variables and session secret
- Created docker/dev/.env.example with Telegram configuration template
- Created docker/prod/.env.example with production environment template
- Moved secrets from docker-compose.yml to .env files (gitignored)
- Changed docker/dev/docker-compose.yml to use placeholders: ${TELEGRAM_BOT_TOKEN}
Security Enhancements:
- Disabled test message on server start by default (TELEGRAM_SEND_TEST_ON_START=false)
- Extended pre-commit hook to detect hardcoded Telegram secrets
- Hook prevents commit if TELEGRAM_BOT_TOKEN or TELEGRAM_CHAT_ID are hardcoded
- All secrets must use environment variable placeholders
Phase 5 fully completed and documented.
14 lines
495 B
Plaintext
14 lines
495 B
Plaintext
# Docker Compose Environment Variables for Development
|
|
# Copy this file to .env and adjust values
|
|
|
|
# Telegram Bot Configuration (optional)
|
|
TELEGRAM_ENABLED=false
|
|
TELEGRAM_SEND_TEST_ON_START=false
|
|
# Bot-Token from @BotFather
|
|
# Example: 123456789:ABCdefGHIjklMNOpqrsTUVwxyz1234567890
|
|
TELEGRAM_BOT_TOKEN=your-bot-token-here
|
|
# Chat-ID of the Telegram group (negative for groups!)
|
|
# Get via: https://api.telegram.org/bot<TOKEN>/getUpdates
|
|
# Example: -1001234567890
|
|
TELEGRAM_CHAT_ID=your-chat-id-here
|