How suitenumerique/drive works
Project type and purpose
• This is a full-stack, self-hosted collaborative file-sharing web application.
• Frontend: Next.js/React (src/frontend)
• Backend: Django REST API + Celery tasks (src/backend)
• Infrastructure: Docker + Docker Compose + Kubernetes Helm charts
File structure
• Top-level “src” splits into “backend” and “frontend.”
• Backend follows Django + Django REST Framework patterns: apps under core, settings, wsgi, celery_app.
• Celery: async tasks for deletion, media cleanup, etc.
• Frontend: Next.js app with pages, features, layouts, UI components.
• Docker & compose.yaml orchestrate containers: app-dev, nginx, db, broker, celery, mail, PostHog.
• Helm charts (src/helm) define Kubernetes resources for backend, frontend, services, ingress.
• Mail templates in “src/mail” generate transactional emails.
Extract insights from the README
• Confirms Next.js + Django REST Framework, Docker-Compose development.
• Emphasizes self-host, scalable, secure file storage.
• Mentions Django admin, translation, Crowdin for i18n.
Detailed capture of essential elements
• Environment config layer (env.d) as annotation to show configuration-driven deployment.
• How Docker Compose mirrors Helm charts: mapping each container to a Kubernetes Deployment + Service.
• Celery tasks (item deletion, document generation) to show where background processing lives.
• Crowdin sync steps feeding into i18n pipelines (optional).