Add configuration template files (.env.example, .dockerignore)
Added essential configuration templates that were missing from the repository due to overly restrictive .gitignore patterns. Changes to .gitignore: - Added negation patterns for .env.example files - Added negation patterns for .dockerignore files - These are safe template files with placeholder values Files added: - .env.example (root): Main environment configuration template - reports-app/backend/.env.example: Backend configuration template - reports-app/frontend/.env.example: Frontend configuration template - reports-app/telegram-bot/.env.example: Telegram bot config template - reports-app/telegram-bot/.dockerignore: Docker build exclusions These template files help developers quickly set up their local development environment by copying and customizing them. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
76
reports-app/telegram-bot/.env.example
Normal file
76
reports-app/telegram-bot/.env.example
Normal file
@@ -0,0 +1,76 @@
|
||||
# ============================================================================
|
||||
# ROA2WEB Telegram Bot - Environment Configuration
|
||||
# ============================================================================
|
||||
# Copy this file to .env and fill in your actual values
|
||||
# IMPORTANT: Never commit .env file to git!
|
||||
|
||||
# ============================================================================
|
||||
# REQUIRED CONFIGURATION
|
||||
# ============================================================================
|
||||
|
||||
# Telegram Bot Configuration
|
||||
# Obtain from @BotFather on Telegram
|
||||
TELEGRAM_BOT_TOKEN=your_bot_token_here
|
||||
|
||||
# Claude Authentication Configuration
|
||||
# ============================================================================
|
||||
# You have TWO options for Claude authentication:
|
||||
#
|
||||
# OPTION 1: API Key (pay per token - requires API credits)
|
||||
# - Get API key from: https://console.anthropic.com/
|
||||
# - Set CLAUDE_API_KEY below
|
||||
# - You will be charged per API usage (separate from Claude subscription)
|
||||
#
|
||||
# OPTION 2: Claude Pro/Max Subscription (RECOMMENDED if you have subscription)
|
||||
# - If you have Claude Pro or Claude Max subscription
|
||||
# - Run: claude-code login (one-time setup)
|
||||
# - Leave CLAUDE_API_KEY empty or commented out
|
||||
# - You won't pay extra API credits (uses your existing subscription)
|
||||
#
|
||||
# For development/local usage: Use Option 2 if you have subscription
|
||||
# For Docker/production: Use Option 1 (API key is simpler in containers)
|
||||
# ============================================================================
|
||||
|
||||
# OPTION 1: Set this if using API key
|
||||
CLAUDE_API_KEY=
|
||||
|
||||
# OPTION 2: Leave empty and run "claude-code login" before starting bot
|
||||
|
||||
# Backend API URL
|
||||
# Development: http://localhost:8001
|
||||
# Docker: http://roa-backend:8000
|
||||
BACKEND_URL=http://roa-backend:8000
|
||||
|
||||
# ============================================================================
|
||||
# DATABASE CONFIGURATION
|
||||
# ============================================================================
|
||||
|
||||
# SQLite Database Path (STANDALONE)
|
||||
# This is where user data, auth codes, and sessions are stored
|
||||
# Development: ./data/telegram_bot.db
|
||||
# Docker: /app/data/telegram_bot.db
|
||||
SQLITE_DB_PATH=/app/data/telegram_bot.db
|
||||
|
||||
# ============================================================================
|
||||
# NETWORKING CONFIGURATION
|
||||
# ============================================================================
|
||||
|
||||
# Internal API Port (for backend to call telegram-bot)
|
||||
# This port is used by the backend to save auth codes
|
||||
INTERNAL_API_PORT=8002
|
||||
|
||||
# ============================================================================
|
||||
# OPTIONAL CONFIGURATION
|
||||
# ============================================================================
|
||||
|
||||
# Logging Level
|
||||
# Options: DEBUG, INFO, WARNING, ERROR, CRITICAL
|
||||
LOG_LEVEL=INFO
|
||||
|
||||
# Sentry DSN for error monitoring (optional)
|
||||
# Get from: https://sentry.io/
|
||||
SENTRY_DSN=
|
||||
|
||||
# Environment
|
||||
# Options: development, production
|
||||
ENVIRONMENT=production
|
||||
Reference in New Issue
Block a user