How toviaferna/turbo-potato works
Project type and purpose
• Turbo-Potato is a Python/Django full-stack web application—a modular monolith—designed to manage agricultural operations (farming, inventory, sales, finance, supplies), user authentication, reporting and documentation.
• It is packaged for containerized deployment (Docker, Gunicorn, Nginx, Heroku/Procfile) and includes both a runtime web app and a static user-guide site (MkDocs).
File structure
• Top level:
• apps/ – Django “apps” (authentication, documentation, farming, finance, home, inventory, reports, sales, supplies)
• core/ – project settings, WSGI/ASGI, common utilities, templates, staticfiles config
• templates/ & apps/*/templates/ – Jinja/Django templates for UI
• apps/static/ & core/staticfiles/ – CSS/JS/image assets
• docs/ + site/ – MkDocs source and generated static site
• Dockerfile, docker-compose.yml, nginx/, gunicorn-cfg.py, Procfile – container and deployment config
• manage.py, requirements.txt – Django CLI and dependencies
README for insights
• Confirms Django usage, local development commands, virtual-env setup, migrations, runserver.
Detail without over-splitting
• Static asset paths and template rendering flow at a high level.
• Deployment units (Docker containers, services) vs. logical components (apps, database).