How taigaio/taiga-back works
Project type and purpose
• This is the Taiga backend: a monolithic, modular Django REST API that powers Taiga.io.
• Its purpose is to serve as the data and business-logic layer for task tracking: it exposes HTTP/JSON endpoints, processes authentication, enforces permissions, handles webhooks and importers, schedules background jobs, sends e-mail and stores attachments.
• It integrates with external services (GitHub, GitLab, Asana, Jira, Trello, Bitbucket), uses Celery for async work, and persists data in PostgreSQL with Django ORM.
File structure
• Top-level orchestrator: manage.py, wsgi.py, settings/ directory holding environment-specific configs.
• Docker folder: Dockerfile, entrypoint scripts, config template for containerizing both Django and Celery.
• Apps under taiga/: auth, base, events, export_import, external_apps, feedback, front, hooks, importers, locale, mdrender, permissions, projects (with submodules attachments, epics, issues, tasks, userstories, wiki, notifications, etc.), searches, stats, telemetry, timeline, users, userstorage, webhooks.
• Asynchronous job definitions: taiga/celery.py, Celery tasks in various apps, RabbitMQ/PostgreSQL backends for events.
• tests/ covering unit and integration for each module.
• Configuration files for CI (pytest.ini, tox.ini), code style (setup.cfg), dependency management (requirements*.txt).
README for additional insights
• Emphasis on API docs, installation guides, contribution guidelines.
• Target audience: backend developers extending or deploying the service.
Elements
• Clear, descriptive labels: “Django API Server,” “Celery Worker,” “PostgreSQL,” “RabbitMQ,” “SMTP,” “S3/Blob Storage.”
• Rectangles for compute containers (API, Workers)