How ader999/nimypine works
Project type and purpose
• This is a full-stack monolithic web application built on Django (Python 3.12, Django 5.1.4).
• Purpose: Provide MIPYMEs with tools to standardize production, manage costs/insumos, calculate lotes, run a resource marketplace, log ventas, manage equipos, and offer an AI-powered asistente.
File structure
• Top-level directories (each a Django app):
• asistente/ – Virtual assistant (api_urls.py, api_views.py, serializers, models)
• cuentas/ – User & company management (custom backends, forms, decorators, management commands)
• marketplace/ – Upload/share/purchase/download resources (models, views, forms)
• produccion/ – Production processes, insumos, formulaciones, ventas (models, serializers, signals)
• mipymes_project/ – Django project config (settings.py, urls.py, wsgi/asgi)
• Shared folders:
• templates/ – HTML templates organized per app
• static/ – CSS, JS, assets
• Configuration/deployment:
• Procfile, runtime.txt (Heroku/Railway), entrypoint.sh, requirements.txt, .env variables for SECRET_KEY, DATABASE_URL, DEBUG.
Key insights from README
• Features map directly to the apps above.
• Uses PostgreSQL in production, SQLite in dev.
• Auth via Django auth, role-based access.
• Future roadmap includes payment, notifications, analytics.
Detail
• How URL routing delegates to either a view (HTML) or an API view (JSON)
• User roles and where RBAC is enforced (e.g., cuentas/backends)
• Major flows: user login, data CRUD, file upload/download, assistant queries, marketplace transactions