Files
store-scraper-bot/.env.example
T
tiennm99 eb0f79be82 chore: drop migration leftovers, refresh env examples + secret-leak scope
- remove MONGODB_URI from .env.example (Atlas migration done; deleted from
  Vercel cloud env too)
- trim .env.deploy.example to vars actually consumed by deploy scripts
  (Upstash creds were only needed by the now-deleted migration script)
- README config table: drop ENV / SOURCE_COMMIT / SCHEDULE_CHECK_APP_TIME
  (never read by code; Java-era leftovers)
- check-secret-leaks: drop MONGODB_URI; add UPSTASH/KV/CRON tokens; widen
  scan roots to include api/
- add scripts/list-upstash-keys.js read-only ops helper
2026-05-10 00:23:16 +07:00

22 lines
834 B
Bash

# Telegram
TELEGRAM_BOT_TOKEN=your_bot_token_here
TELEGRAM_BOT_USERNAME=your_bot_username
TELEGRAM_WEBHOOK_SECRET=generate_a_random_string_at_least_32_chars
# Upstash Redis (REST API; same DB can be shared with other Vercel projects
# because KEY_PREFIX namespaces this bot's keys).
# If the Vercel Marketplace Upstash integration is enabled, the project will
# already have KV_REST_API_URL and KV_REST_API_TOKEN — the adapter accepts
# those as fallbacks, so duplication is optional.
UPSTASH_REDIS_REST_URL=https://xxx.upstash.io
UPSTASH_REDIS_REST_TOKEN=your_upstash_rest_token
KEY_PREFIX=store-scraper-bot:
# Vercel Cron auth — protects /api/cron from random POSTs.
CRON_SECRET=generate_another_random_string_at_least_32_chars
# Bot config
ADMIN_IDS=123456789,987654321
APP_CACHE_SECONDS=600
NUM_DAYS_WARNING_NOT_UPDATED=30