Download the PHP package anwargazi/ci-laravel-support without Composer
On this page you can find all versions of the php package anwargazi/ci-laravel-support. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download anwargazi/ci-laravel-support
More information about anwargazi/ci-laravel-support
Files in anwargazi/ci-laravel-support
Package ci-laravel-support
Short Description Native Laravel 8 runtime bridge for incrementally migrating CodeIgniter 3 applications.
License proprietary
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package ci-laravel-support
CI to Laravel 8 bridge
anwargazi/ci-laravel-support lets a legacy CodeIgniter 3 application and a
real Laravel 8 application share one public front controller. It is designed
for route-by-route migrations where running a second PHP service or moving the
whole application at once is not practical.
Laravel-owned requests run Laravel's native HTTP kernel. Requests that are not owned by Laravel return to the original CodeIgniter bootstrap unchanged. Only one framework is booted for any request.
This is a bounded migration runtime. PHP 7.3, Laravel 8, and SwiftMailer are end-of-life. Read the security policy before production use.
Start here
| If you need to... | Read... |
|---|---|
| Understand the design and request flow | Architecture |
| Install the bridge in a CI3/Laravel host | Installation |
| Look up every configuration option | Configuration reference |
| Move an endpoint from CI3 to Laravel | Route migration guide |
| Develop or test this package | Development guide |
| Release, deploy, verify, or roll back | Deployment and operations |
| Diagnose a failure | Troubleshooting |
| Maintain the older CI-side helper layer | Legacy compatibility API |
| Review security exceptions | Security policy |
| Review release history | Changelog |
The documentation index provides role-based reading paths.
Runtime contract
- PHP: exactly
7.3.x; dependency resolution and tests target7.3.33. - Laravel Framework: exactly
8.83.29. league/commonmark: exactly1.4.3, with the supplied resource-limit patch.- One public front controller, virtual host, and PHP-FPM service.
- One framework booted per request.
- Separate Composer dependency trees for CI3 and Laravel are strongly recommended.
The service provider checks this contract whenever Laravel boots. A version change or missing patch marker fails closed.
How routing works
The dispatcher does not load Composer or either framework until it has matched
the request against a cached manifest. The manifest comes from Laravel's real
route collection, preserving path constraints, domains, schemes, methods, and
Laravel's 405 Method Not Allowed ownership behavior.
Minimal installation outline
- Place a standard Laravel 8 application beside the legacy CI3 application.
- Merge the host Composer fragment
into Laravel's
composer.jsonand copy both files frompatches/. - Resolve dependencies and verify the pinned runtime.
- Publish the bridge config and front-controller example.
- Add the dispatcher block at the very top of CI's
index.php. - Add native Laravel routes and compile the ownership manifest.
Follow the full installation guide before deployment.
Commands
| Command | Purpose |
|---|---|
php artisan ci-bridge:verify-runtime |
Verifies exact dependency versions and security patch markers. |
php artisan ci-bridge:cache-routes |
Atomically regenerates route ownership. |
php artisan ci-bridge:cache-routes --path=/absolute/file.php |
Uses a controlled alternate manifest path. |
composer test |
Runs PHPUnit and the dependency-free legacy regression suite. |
Important boundaries
- Laravel and CI3 do not automatically share containers, sessions, authentication, CSRF tokens, configuration, exception handling, or logs.
- Keep Laravel fallback routes disabled while CI3 owns any route.
- Regenerate the manifest after every route or route-provider change. A missing
or invalid manifest returns
503; the bridge never guesses. - The bridge does not provide cross-framework authentication. Build and test an application-specific handoff when Laravel must recognize a CI login.
- The legacy compatibility API is retained for old CI-side integrations; it is not part of the native Laravel request path.
Recommended layout
The web root remains the legacy application's entrypoint. The Laravel directory
is not a second site and does not require artisan serve.
Quick verification
In a host application, test a Laravel route, a representative CI route, and an unsupported method on the Laravel URI. See the complete deployment checklist.
License
This project is source-available, not open-source software. The custom Personal and Non-Profit License permits personal use and modification, and non-profit redistribution under the same unmodified license. Every redistribution must provide prominent, publicly visible credit to the original developer. Professional or for-profit use requires prior written permission from Minhajul Anwar at [email protected].
Developer contact
- Name: Minhajul Anwar
- Email: [email protected]
- Location: Bangladesh
All versions of ci-laravel-support with dependencies
php Version ~7.3.0
laravel/framework Version 8.83.29
league/commonmark Version 1.4.3