Weave Code
Core Laravel Package
tastyigniter/core
Core code for TastyIgniter, a professional restaurant platform for online food ordering and table reservations. Powers the TastyIgniter application and extensions with a Laravel-based framework for building custom ordering systems.
Core package for TastyIgniter. Provides the foundational modules, admin panel, and extension system powering the TastyIgniter application.
Frequently asked questions about Core
- What is tastyigniter/core used for?
- tastyigniter/core is the foundational package for TastyIgniter, a Laravel-based restaurant platform for online food ordering and table reservations. It provides the admin panel, extension system, media handling, core workflows such as orders and reservations, and the framework used by TastyIgniter extensions. It is intended for building or powering a TastyIgniter application rather than as a general-purpose Laravel package.
- How do I install tastyigniter/core in a Laravel project?
- Install it with Composer using composer require tastyigniter/core:^4.4.5, then run the database migrations and seeders for the TastyIgniter application. Configure the admin panel via config/admin.php, publish required assets with php artisan vendor:publish, and install extensions such as tastyigniter/cart as needed. For a full application, the recommended starting point is the TastyIgniter application repository rather than adding core to an arbitrary Laravel app.
- Which Laravel and PHP versions does tastyigniter/core support?
- The package is reported as well-tested with Laravel 10, 11, and 12. It supports PHP 8.3 through 8.4, which keeps versioning risk relatively low for modern Laravel deployments. Check the package constraints before upgrading if your application pins older Laravel or PHP versions.
- Is tastyigniter/core only for restaurant and food ordering apps?
- The package is opinionated toward the restaurant domain, including orders, reservations, menus, and related admin workflows. You can reuse some components such as the admin panel, media management, and extension system for other use cases, but non-food-and-beverage projects may require significant refactoring. It is not recommended for non-Laravel projects because it assumes Laravel routing, service container, Eloquent, and Blade.
- How does the TastyIgniter extension system work?
- tastyigniter/core uses a plugin-based extension system that supports dynamic loading of modules such as Cart and Reservations, typically installed via Composer. Extensions integrate with Laravel conventions and lifecycle events, allowing features like checkout, reservations, and admin widgets to be added without modifying the core. The approach is well suited to restaurant workflows that need POS integrations, loyalty programs, or other custom features.
- Can I customize or hide the TastyIgniter admin panel navigation?
- Yes. The admin panel supports configuration through config/admin.php, custom Blade themes, permissions, widgets, and navigation controls. In v4.4.5, the suppressNavigation option on AdminController lets you hide the header and sidebar for custom admin layouts. This is useful when building focused admin screens or embedding TastyIgniter admin views in a different layout.
- What are the main production risks of using tastyigniter/core?
- The biggest risk is tight coupling to the restaurant domain, so repurposing it for non-F&B SaaS or event management may require substantial refactoring. External API dependencies such as Google Places and Nominatim can introduce latency and cost concerns, so plan for caching and failure handling. Also review custom extensions before upgrading to v4.4.5 because enshrined/svg-sanitize moved from ^0.22 to ^1.0, which may break code relying on the old sanitizer API.
- Does tastyigniter/core support currencies, languages, and geolocation?
- Yes. It includes built-in language, country, and currency management with indexed database tables for performance, and it supports zero-decimal currencies. Geolocation features integrate with services such as Google Places and Nominatim. These features are oriented around restaurant ordering and reservation use cases rather than a generic multi-tenant SaaS platform.
- How should I test tastyigniter/core after upgrading to v4.4.5?
- Run migrations and exercise the admin panel, including any controllers using the new suppressNavigation option. Test Artisan commands and confirmation prompts because v4.4.5 includes CLI bug fixes. If you maintain custom extensions, verify any direct use of enshrined/svg-sanitize v0.22 APIs and test media uploads, sanitization, geolocation, and payment flows before deploying.
- What are alternatives to tastyigniter/core for Laravel ordering systems?
- Alternatives depend on whether you need a complete restaurant platform or only selected components. You can build a custom Laravel application with Eloquent, Blade, and your own admin panel, or evaluate other Laravel ecommerce and booking packages if the restaurant-specific workflows are not essential. tastyigniter/core is strongest when you want TastyIgniter's existing admin panel, extension system, ordering, and reservation features.
Weaver
How can I help you explore Laravel packages today?