All checks were successful
CI / lint-and-test (push) Successful in 14s
- Introduced a new i18n module for managing translations and language normalization, supporting both Russian and English. - Updated various handlers and services to utilize the new translation functions for user-facing messages, improving user experience based on language preferences. - Enhanced error handling and response messages to be language-aware, ensuring appropriate feedback is provided to users in their preferred language. - Added tests for the i18n module to validate language detection and translation functionality. - Updated the example environment file to include a default language configuration.
21 lines
793 B
Plaintext
21 lines
793 B
Plaintext
BOT_TOKEN=your_bot_token_here
|
|
DATABASE_URL=sqlite:///data/duty_teller.db
|
|
MINI_APP_BASE_URL=
|
|
HTTP_PORT=8080
|
|
|
|
# Miniapp access: comma-separated Telegram usernames (no @). Empty = no one allowed.
|
|
ALLOWED_USERNAMES=username1,username2
|
|
ADMIN_USERNAMES=admin1,admin2
|
|
|
|
# Dev only: set to 1 to allow calendar without Telegram initData (insecure; do not use in production).
|
|
# MINI_APP_SKIP_AUTH=1
|
|
|
|
# Optional: URL of a public ICS calendar (e.g. holidays). Days from this calendar are highlighted on the duty grid; click "i" for summary.
|
|
# EXTERNAL_CALENDAR_ICS_URL=https://example.com/holidays.ics
|
|
|
|
# Timezone for the pinned duty message in groups (e.g. Europe/Moscow).
|
|
# DUTY_DISPLAY_TZ=Europe/Moscow
|
|
|
|
# Default UI language when user language is unknown: en or ru (default: en).
|
|
# DEFAULT_LANGUAGE=en
|