How gallant-giri/civicscan works
Project type and purpose
• This is a monolithic full-stack web application built with Django (Python).
• Purpose (inferred from name “CivicScan” and the apps): it lets users sign up, submit and view civic reports (with photos), and browse a landing “homepage.”
File structure
• Top-level “manage.py”, “db.sqlite3”, “.env”, “render.yaml” → classic Django project with a local SQLite DB and deployment configured (likely on Render).
• The “BrillianBengaluru” directory holds the Django project settings (settings.py, urls.py, wsgi.py, asgi.py).
• Three Django apps:
• homepage/ → landing pages, static index, anonymous report entry
• reports/ → core report submission, map view, management commands (e.g., update_addresses.py)
• users/ → custom user models, signup, dashboard
• Static assets: “static/” is the development assets; “staticfiles/” contains collected admin and Cloudinary-related JS/CSS (indicating Cloudinary used for media uploads).
• media/ → local storage for uploads (under “media/uploads” and “media/reports_photos”).
• Templates are organized per app under “templates/…/[app_name]/”.
• render.yaml → deployment spec (likely container, services, environment variables).
README
• Minimal content (“# CivicScan”) but the name plus file tree shows it’s a civic reporting platform.
Detail
• Django app as its own component.
• Both local media folder and Cloudinary to reflect actual config.
• Management command pipeline (e.g., background address updates).
• If desired, annotate the deployment block with render.yaml settings (service, environment).