Examples and instructions for using Laravel's Illuminate components as standalone libraries in non-Laravel PHP applications.
Torch is a project that provides examples and instructions for using Laravel's Illuminate components as standalone libraries in non-Laravel PHP applications. It solves the problem of developers wanting to leverage specific Laravel packages like Eloquent ORM, Blade templating, or the Artisan console without adopting the entire Laravel framework. Each component is demonstrated with runnable code samples that can be integrated into other PHP projects.
PHP developers working with non-Laravel frameworks (e.g., Slim, Symfony, or custom setups) who want to incorporate specific Laravel components into their applications. It's also useful for developers maintaining legacy projects who need guidance on using older Illuminate versions.
Developers choose Torch because it offers practical, tested examples for each Illuminate component, reducing the learning curve and integration effort. Unlike official Laravel documentation, Torch focuses specifically on standalone usage, making it the go-to resource for framework-agnostic Laravel component adoption.
Examples of using each Illuminate component in non-Laravel applications
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Each major Illuminate component, like Database, Cache, and View, has a runnable demo in its own directory, often using Slim, making it easy to test and adapt.
Focused on non-Laravel applications, with examples that work in any Symfony-HttpFoundation-compatible project, as stated in the philosophy.
Includes branches for multiple Illuminate versions (8.0, 5.5, 5.1, 4.2), helping developers migrate or maintain older projects, as noted in the README.
Contribution guidelines emphasize implementing components without Laravel's Service Providers where possible, promoting clean, standalone usage.
Some components, like Mail, are listed as 'Need to be moved over from 4.2' and lack updated examples, limiting usability for certain features.
Each example requires navigating to its directory, running composer install, and starting a PHP server, which can be cumbersome for testing multiple components.
The contributing section notes that readme's need updates for testing instructions, indicating some examples may lack detailed guidance.