How yashbakadiya/myblog works
Project type and purpose
• This is a full-stack web application built with Django (Python).
• Purpose: provide user authentication (registration, login, logout, password reset, profile management) and blogging functionality (create, edit, delete, list, view posts).
File structure
• Top-level:
• manage.py – Django CLI entry point
• django_project/ – project configuration (settings.py, urls.py, wsgi.py, asgi.py)
• blog/ – “blog” app: models, views, forms, templates, static assets, migrations
• users/ – “users” app: models, views, forms, templates, signals, migrations
• db.sqlite3 – development database
• requirements.txt, Procfile – dependency list & Heroku deployment
• Patterns & architecture:
• Two Django “apps” plugged into a shared project
• MVT (Model-View-Template) pattern
• Static files served under blog/static and users/templates
• URL routing delegated to each app via include() in project urls.py
README for additional insights
• Confirms multi-app setup, URL endpoints for auth and blog
• No external microservices, but email backend used for password resets
• Deployment targets: local dev server, possibly Heroku (Procfile)
• Presentation layer (templates, static) – e.g., blue
• Application layer (views, business logic) – e.g., green
• Data layer (database, migrations) – e.g., orange
• External services (SMTP, CDN) – e.g., gray
Detail
• Middleware (authentication, CSRF, session) between request ingestion and view execution
• Signal handlers triggered on user model events
• Django admin as a separate UI path into the Django Project
• Environment/config store (myEnvVal.py) feeding into settings