How mahmoud-mh/macropulse works
Project type and purpose
• MacroPulse is a full-stack web application:
• React/Vite frontend (SPA for task and indicator management)
• Django REST API backend (monolithic Django project with multiple apps)
• Celery + Redis for background task processing
• PostgreSQL as the primary data store
• Django Channels (WebSocket) for real-time updates
• External integration with FRED API
File structure
• Top‐level:
• frontend/ – React app (TypeScript, Vite)
• macro_pulse/ – Django project (settings, routing, ASGI/WGI, Celery config)
• authentication/, indicators/, websocket/ – Django “apps” implementing auth, indicator logic, real-time channels
• manage.py, Dockerfile, docker-compose.yml – orchestration & deployment
• requirements.txt – backend dependencies
• Patterns & roles:
• authentication/ – JWT auth, middleware, token store
• indicators/ – FRED API integration, data models, serializers, Celery tasks, admin templates
• websocket/ + macro_pulse/consumers.py + routing.py – Channels routing for live updates
• celery tasks & beat under indicators/ and macro_pulse/celery.py
Insights from README
• Clearly separates Frontend vs. Backend responsibility
• Backend features: Task Manager, Indicator Service, Auth System, WebSocket Service