How fvenegas-v/nexus_tcg works
Project type and purpose
• Nexus TCG is a full-stack, cross-platform mobile application (Flutter) backed by a monolithic Django REST API.
• It connects trading-card-game players into communities, supports posts/comments/reactions, and computes user reputation with anti-gaming protections.
File structure
• Top-level “lib/” holds the Flutter front-end, organized by core (config, models, providers, services, widgets) and feature modules (auth, communities, posts, reputation, etc.).
• Top-level “backend/” is a Django project with apps: communities, users, games, nexus_api (project settings), Celery tasks, management commands, media storage, templates, and tests.
• Infrastructure/config files: Dockerfile(.dev), docker-compose.yml, GitHub Actions workflows, .env.example, and docs in docs/specs and docs/uml.
README for additional insights
• README explicitly lists technologies: Flutter/Dart on front, Django/DRF on back, SQLite dev vs PostgreSQL prod, Redis/Celery for async tasks, JWT auth, CI/CD via GitHub Actions, Docker Compose multi-service setup, adminer, and email via SMTP.
• It even sketches the folder layout for frontend.
Details to capture
• Frontend modules and state providers (optional detail)
• Celery tasks for image processing, anti-gaming, email sending
• Data flows for media uploads (HTTP → Django → file storage under media/ → served back)
• Authentication flow (Login → JWT issued → subsequent API calls)
• CI/CD flow (GitHub Actions → Docker images → staging)