How juancarsp7/devstagram works
Project type and purpose
• This is a full-stack, monolithic Laravel web application implementing a simple social network. Users can register, authenticate, create posts and code snippets (“codigos”), comment, like, follow/unfollow, upload images, and receive email notifications.
• Key use cases: user registration/login, CRUD on posts/“codigos”/comments, real-time or AJAX-driven likes (via Livewire), follower relationships, email notifications, file uploads, a scheduling/queue system for background jobs.
File structure
• Top-level directories:
• app/: contains MVC code (Controllers, Models, Middleware, Mail, Notifications, Livewire components, Policies, Console commands, Providers)
• config/: application configuration (database, mail, cache, queues, broadcasting, services)
• database/: migrations, model factories, seeders
• resources/: frontend assets (CSS/JS via Vite), Blade view templates, localization files
• public/: web root (index.php, assets, uploads)
• routes/: routing definitions (web.php, api.php, console.php, channels.php)
• storage/: runtime files (logs, cache, sessions, uploaded files)
• bootstrap/: framework bootstrap and cached configs
• tests/: Unit and Feature tests
• Framework conventions: service providers, Facades, Eloquent ORM, Blade + Livewire for dynamic UI, queued Mail & Notifications, Scheduler (app/Console/Kernel.php).
README for additional insights
• It’s the standard Laravel README describing framework features. No custom architecture docs are present.
Details
• Every essential flow: HTTP, AJAX (Livewire), file upload, email dispatch, scheduled tasks.
• Configuration boundaries (config/*.php) feeding into service providers.
• Queue driver and cache driver selections.
• Avoid over-splitting; modularize by function (web requests, tasks, data).