How abhaybabbar/chatrooms works
Project type and purpose
• This is a full-stack Django web application with two Django apps:
• auth_app – handles user signup, login, sessions, forms, templates
• chat – implements real-time chatrooms using Django Channels (websockets), models, routing, templates
• The README shows a screenshot of the chat UI and mentions hosting via ngrok, confirming it’s a real-time chat system accessible over HTTP/WebSocket.
File structure
• Top-level:
• chatroom/ – Django project settings (asgi.py, wsgi.py, settings.py, urls.py, routing.py)
• auth_app/ – authentication app
• chat/ – chatroom app
• manage.py, requirements.txt
• Key configuration files:
• chatroom/asgi.py & routing.py – entrypoint for HTTP + WebSocket protocols
• chatroom/settings.py – lists INSTALLED_APPS, CHANNEL_LAYERS, database settings
• chat/routing.py – WebSocket URLRouter
• Patterns:
• MVC/MVT – views/templates/models in each app
• Asynchronous consumers for real-time features
• A channel layer (likely Redis) sits between consumers and the Django application
README
• Minimal text, but screenshot and ngrok mention implies public exposure of both HTTP and WS endpoints