Migrate from local Supabase stack to external Supabase instance
- Reduce docker-compose from 6 services to 1 (worker only) - Connect via supavisor pooled port (6543) on dedicated Supabase - Add willhaben_tracker schema with search_path in asyncpg pool init - Create consolidated migration SQL for Supabase SQL Editor - Update .env.example with new connection pattern
This commit is contained in:
+4
-5
@@ -1,14 +1,13 @@
|
||||
# Telegram Bot Token (from @BotFather)
|
||||
TELEGRAM_BOT_TOKEN=your-bot-token-here
|
||||
|
||||
# PostgreSQL Credentials
|
||||
# Supabase PostgreSQL Connection (pooled via supavisor on port 6543)
|
||||
POSTGRES_HOST=192.168.178.3
|
||||
POSTGRES_PORT=6543
|
||||
POSTGRES_USER=postgres
|
||||
POSTGRES_PASSWORD=change-me-strong-password
|
||||
POSTGRES_PASSWORD=your-supabase-db-password
|
||||
POSTGRES_DB=postgres
|
||||
|
||||
# PostgREST JWT Secret (random string for signing tokens)
|
||||
JWT_SECRET=your-super-secret-jwt-key-change-in-production
|
||||
|
||||
# Worker Configuration
|
||||
DEFAULT_INTERVAL_MINUTES=60
|
||||
ADMIN_TELEGRAM_IDS=123456789 # Comma-separated Telegram user IDs with admin access
|
||||
|
||||
Reference in New Issue
Block a user