How bharath6911/cinenest works
Project type and purpose
• CineNest is a full‑stack, LAMP‑style streaming platform (inspired by Netflix/Prime) that combines static front‑end pages (HTML/CSS/JS), a PHP backend for user auth (log.php, register.php), and a MySQL database. It also has PWA assets (manifest, service worker) and even an Android wrapper (CineNest.apk).
File structure
• Top‑level web files:
• index.html, h.html, player.html – main pages & player interface
• styles.css – global stylesheet
• j.js, player.js – front‑end scripts for UI behavior and video player logic
• log.php, register.php – backend authentication endpoints
• log.html – login form page (static)
• image/ – folder of poster assets
• CineNest.apk sits alongside these as a packaged PWA wrapper for Android.
• No native “src” or “lib” folders: it’s a monolithic repo with static + PHP files in root.
README for additional insights
• Backend: PHP + MySQL on InfinityFree (via phpMyAdmin)
• Hosting: Render.com for static/PHP, InfinityFree for database
• External services: The Movie Database API for posters/ratings, Streamtape for video streams
• PWA readiness: manifest.json + service-worker.js enable offline caching and installability
Elements
• Labels: e.g., “Client Browser”, “Android App (APK)”, “Web Server (PHP)”, “MySQL DB”
• Client components in blue (browser, APK)
• Front‑end/PWA assets in light green
• Backend/PHP in orange
• External services in gray