munlaly/webgurus-nyarigyak-1csoport

Purpose and Shape

This is an early-stage meal-planning and recipe/inventory application built on Laravel. The domain schema exists, but HTTP controllers and application routes are effectively skeletal. A separate Nuxt frontend is scaffolded, while Laravel also retains its default Vite/Vue frontend scaffold.

Entry Points and Runtime

Laravel serves HTTP requests through public/index.php, bootstraps application bindings and middleware in bootstrap/app.php, and defines web endpoints in routes/web.php. CLI and scheduled/console commands enter through artisan and routes/console.php.

The backend runtime is PHP/Laravel with Composer dependencies (composer.json). Local development is configured for DDEV in .ddev/config.yaml. The browser-facing frontend may be independently run as Nuxt from frontend/nuxt.config.ts.

Domain Persistence Model

Eloquent models define the core meal-planning data graph:

• Recipe catalog and classification: app/Models/Recipes.php, app/Models/Category.php, app/Models/Ingredients.php.

• Recipe-to-ingredient association: app/Models/RecipeIngredient.php.

• Per-user state: app/Models/User.php, app/Models/UserInventory.php, app/Models/UserSettings.php.

• Planned meals: app/Models/MealPlan.php.

Database structure is authored through corresponding migrations, especially database/migrations/2026_08_06_205202_create_recipes_table.php, database/migrations/2026_08_06_205230_create_recipe_ingredients_table.php, and database/migrations/2026_08_06_205301_create_meal_plans_table.php.

Primary Intended Data Flow

The intended business flow is: authenticated user → user settings and inventory → select recipes composed of ingredients → create meal-plan records. Recipe ingredients form the key boundary between the global recipe catalog and user-specific inventory/planning data. Persistence is mediated by Laravel Eloquent models, with connection settings centralized in config/database.php.

No domain orchestration layer, API controllers, or concrete request handlers are present beyond the base app/Http/Controllers/Controller.php; implementing these is the main missing application layer.

Authentication and User Boundary

Laravel’s standard user foundation is present in app/Models/User.php and database/migrations/0001_01_01_000000_create_users_table.php. Authentication behavior is configured in config/auth.php. User-owned inventory, settings, and plans should be authorization-scoped at the controller/service boundary before querying or mutating their associated models.

Presentation Boundaries

Two frontend paths coexist:

• Laravel/Vite/Vue scaffold: resources/js/app.js, resources/js/App.vue, vite.config.js.

• Standalone Nuxt application scaffold: frontend/app/app.vue, frontend/nuxt.config.ts.

Neither tree, from the available structure, establishes an explicit backend API contract. Decide whether Nuxt consumes Laravel APIs or whether Laravel serves the Vite application before extending UI work, to avoid parallel frontend ownership.

Platform Services

Laravel configuration exposes database, cache, sessions, filesystem storage, mail, logging, and queues through config/database.php, config/cache.php, config/session.php, config/filesystems.php, config/mail.php, and config/queue.php. Default cache and jobs schema migrations exist, so asynchronous work can be introduced for future plan generation or notifications, but no jobs are currently implemented.