How puneethreddyhc/online-shopping-system-advanced works
Project type and purpose
• This is a monolithic, full-stack LAMP-style e-commerce web application.
• Purpose: public storefront (browsing products, cart, checkout, orders, reviews) plus an advanced admin console (user management, product CRUD, orders, sales reports).
File structure
• Top-level PHP files (index.php, product.php, cart.php, checkout.php, etc.) form the public site.
• “admin/” folder contains a parallel PHP application for administrators, including layout (assets/css, js, scss), page logic (add_products.php, orders.php), and shared includes (admin/includes/db.php).
• Shared configuration: config.php, db.php, database/onlineshop.sql.
• Static assets: css/, js/, img/, product_images/.
• No microservices—single Apache/PHP runtime with MySQL.
Main components
A. Clients (Web browsers, mobile)
B. Web Server (Apache + PHP runtime)
– Public module (index.php, cart.php, checkout.php, product.php, review_action.php, etc.)
– Admin module (admin/index.php, admin/add_products.php, admin/orders.php, etc.)
– Shared code (config.php, db.php, common includes, product_images storage)
C. Database Server (MySQL)
– Tables: users, products, orders, order_items, reviews, wishlist, suppliers, etc.
D. External services
– Email SMTP for newsletter/offers (newslettter.php, offersmail.php)
– (Optional) Payment gateway endpoint if integrated in checkout_process.php
Relationships and data flows
• Client ←→ Web Server via HTTP/S
– Public HTTP routes → Public module → DB queries → HTML/CSS/JS responses
– Admin HTTP routes (under /admin) → Admin module → DB queries → Admin UI
• Web Server → MySQL over TCP
• Web Server → SMTP server for transactional emails
• File storage: product_images served directly by web server
Architectural patterns and design principles
• Monolithic MVC-style with “controller” PHP pages, “view” includes (header.php, footer.php), and simple “model” via db.php abstraction.
• Clear separation of public vs. admin contexts (separate directories, sessions, authentication).
• Reusable shared components: CSS/JS assets, PHP includes for database connection and header/footer.
• Session-based user authentication for both users and admin.