tt

CELERY_SCHEDULING_SETUP.md

@@ -31,6 +31,38 @@ sudo systemctl start redis
 sudo systemctl enable redis
 ```
 
+### 2. Hugging Face Spaces / Production Deployment
+For Hugging Face Spaces or production deployments where you can't run Redis directly:
+
+**Option A: Use Redis Cloud (Recommended)**
+1. Create a free Redis Cloud account at https://redislabs.com/try-free/
+2. Create a Redis database (free tier available)
+3. Update your `.env` file:
+```env
+CELERY_BROKER_URL="redis://your-redis-host:port/0"
+CELERY_RESULT_BACKEND="redis://your-redis-host:port/0"
+```
+
+**Option B: Use Docker Compose**
+```yaml
+# docker-compose.yml
+version: '3.8'
+services:
+  redis:
+    image: redis:7-alpine
+    ports:
+      - "6379:6379"
+    volumes:
+      - redis_data:/data
+    command: redis-server --appendonly yes
+
+volumes:
+  redis_data:
+```
+
+**Option C: Skip Celery (Basic Mode)**
+If Redis is not available, the Flask app will start without Celery functionality. Schedules will be saved but won't execute automatically.
+
 ### 2. Python Dependencies
 Install the required packages:
 ```bash
@@ -133,7 +165,30 @@ celery -A celery_config inspect active
 
 **1. Redis Connection Failed**
 ```
-Solution: Start Redis server first
+Error: Error 111 connecting to localhost:6379. Connection refused
+
+Solutions:
+1. Start Redis server locally (development):
+   Windows: redis-server
+   Linux/Mac: sudo systemctl start redis
+
+2. Use Redis Cloud (production/Hugging Face):
+   - Create free Redis Cloud account
+   - Update .env with Redis Cloud URL
+   - Set CELERY_BROKER_URL and CELERY_RESULT_BACKEND
+
+3. Use Docker Compose:
+   version: '3.8'
+   services:
+     redis:
+       image: redis:7-alpine
+       ports: ["6379:6379"]
+       volumes: [redis_data:/data]
+   volumes: redis_data:
+
+4. Skip Celery (basic mode):
+   - App will start without scheduling functionality
+   - Schedules saved but won't execute automatically
 ```
 
 **2. Tasks Not Executing**

backend/celery_tasks/content_tasks.py

@@ -89,7 +89,7 @@ def generate_content_task(self, user_id: str, schedule_id: str, supabase_client_
             'message': f'Error in content generation: {str(e)}'
         }
 
-@celery.task(bind=True)
+@celery_app.task(bind=True)
 def publish_post_task(self, schedule_id: str, supabase_client_config: dict):
     """
     Celery task to publish a scheduled post.

backend/celery_tasks/schedule_loader.py

@@ -87,7 +87,7 @@ def load_schedules_task():
         logger.info(f"Found {len(schedules)} schedules")
         
         # Get current beat schedule
-        current_schedule = current_app.conf.beat_schedule
+        current_schedule = celery_app.conf.beat_schedule
         
         # Remove existing scheduled jobs (except the loader job)
         # In a production environment, you might want to be more selective about this

backend/celery_tasks/scheduler.py

@@ -1,7 +1,7 @@
 from datetime import datetime, timedelta
 from celery import chain
 import logging
-from backend.celery_app import celery
+from backend.celery_config import celery_app
 from backend.celery_tasks.content_tasks import generate_content_task, publish_post_task
 
 # Configure logging