How ajinkya1718/museum-chatbot works
Project type and purpose
• This is a Python-based, AI-driven chatbot web application for museum ticket booking and visitor information.
• It combines a lightweight HTTP server, a static front-end, an LLM/chat logic layer, analytics, and a payment interface.
File structure
Top-level files and directories:
• server.py – HTTP server entrypoint (likely Flask/FastAPI or built-in HTTP).
• llm.py – encapsulates the large-language-model interactions.
• chatbot.py – conversation management and routing user queries.
• analytics.py – collects usage data, logs interactions or metrics.
• main.py – orchestration script that ties server, chatbot, LLM, and analytics modules.
• index.html + static/… – front-end UI (HTML/CSS/JS) served to the browser.
• payment/index.html – payment gateway front-end template.
• requirements.txt – Python dependencies (e.g., openai, Flask).
README for additional insights
• The README confirms:
• Access via http://localhost:8000
• Launch point: python llm.py (though server.py or main.py may actually start the app in practice)
• Key features: ticket booking (with an embedded payment gateway), FAQs, accessibility info, real-time updates, multilingual support, and data security.
Final advice
• How data flows between browser, server, AI, and payment gateway.
• Security/encryption layer for ticket bookings.
• Keep it detailed but organized in horizontal layers (UI → API → business logic → external).