How rasulkireev/marketing-agents works
Main Components
• Backend (Django Application):
• Core of the project with two key directories: the “seo_blog_bot” folder (containing settings, ASGI/WGSI, URL configurations, and other high-level project utilities) and the “core” folder (which holds the business logic, models, migrations, views, tasks, signals, and API endpoints).
• A component for administrative tools (admin panel as referenced in the README) and Django’s built-in features.
• Frontend:
• Depicted as a separate module under the “frontend” directory. This contains source code (controllers, application logic, styles, templates) and build configurations (Webpack, PostCSS, Tailwind).
• That the templating system bridges server-side rendering (Django templates) with client-side dynamic controllers.
• External Services & Integrations:
• Stripe for payments and subscriptions. Include this external payment gateway showing data flow to and from the backend.
• CapRover deployment environment and integration with CI/CD (GitHub Actions) as per the deployment directions in the README.
• Background workers: Separate container definitions (seo-blog-bot-workers) are indicated in deployment files.
• Database (likely PostgreSQL) and caching or messaging services (Redis) as separate components in the deployment instructions.
Relationships and Interactions
• The frontend communicates with backend API endpoints from “core/api” (e.g., auth, views, schemas).
• Django’s templating system (files in both frontend/templates and core/templates) generates or serves dynamic HTML pages.
• Link the Backend to External Services:
• Demonstrate how Stripe webhooks communicate with the backend (as noted in the README).
• How background tasks (managed via celery-like tasks in core/tasks.py or similar mechanisms) might interact with external queues or worker containers.
• Deployment Infrastructure:
• GitHub Actions workflows that trigger builds and deployments, and their connections to CapRover.
Architectural Patterns and Design Principles
• Separation of Concerns:
• The division between the backend (“core” and “seo_blog_bot”) and the frontend ensures clear modularity.
• MVC and RESTful API:
• Microservices/Multi-container Deployment:
• CI/CD Integration:
• The presence of GitHub workflows (.github/workflows) and Docker Compose is key. Represent these as auxiliary orchestration components that automate deployment, scaling, and versioning.