How vital1tch/virtual-zoo works
Project type and purpose
• This is a monolithic full-stack web application built on Laravel (PHP MVC framework).
• Purpose: “Virtual Zoo” lets users CRUD Animals and Cages, view modals of animals in a cage, handle cage-to-animal relations, issue notifications, and store uploaded images.
File structure
• Top-level:
• app/ — Laravel MVC core (Http/Controllers, Models, Providers)
• config/ — framework and service configs
• database/ — migrations, factories, seeders
• public/ — web root (index.php, CSS, assets)
• resources/ — Blade templates, raw CSS/JS, images
• routes/ — route definitions (web.php, console.php)
• storage/ — cached files, sessions, image uploads
• bootstrap/ — framework bootstrapper
• Patterns:
• MVC (Controllers invoke Models, return Blade Views)
• Eloquent ORM for database
• Blade templating for server-side rendering
• Vite (vite.config.js) to bundle frontend assets
• Config/build/deploy files: .env, composer.json, package.json, artisan, phpunit.xml
Extract README insights
• Features: add/edit/delete Animals & Cages, auto-reassign when deleting filled cages, session-flash notifications, modal windows for list views.
• Tech: Laravel, MySQL (via .env), Blade, JS/CSS assets, storage link for animal photos.
• Components:
• Rectangles grouped by layer (Client, Web Server, Laravel App, Database, File System)
– Blue for client/UI
– Green for Laravel core
– Orange for Database
– Gray for File System & Storage
• Labels:
• Port/URLs if helpful (e.g., 127.0.0.1:8000)