- Is outlandish/rest-bundle a Laravel package?
- No. It is a Symfony bundle built for the Symfony 2.x era, with no Laravel service providers, no Eloquent integration, and no Laravel support. Installing it in a Laravel application is not a supported path.
- Can I install outlandish/rest-bundle with Composer in a Laravel project?
- Composer may resolve the package, but it will not function. Laravel has no bundle registration, no DoctrineBundle, and no AppKernel-style bootstrap, so the package's routing and controller layer never boots. You would end up reimplementing it as Laravel routes and controllers.
- Which Laravel versions does outlandish/rest-bundle support?
- None. The last release was February 2014 and targets the Symfony 2.x era with PHP 5.3 to 5.6 and PSR-0 autoloading. It does not support modern Laravel or modern Symfony versions.
- What does outlandish/rest-bundle actually do?
- It auto-exposes Doctrine entities as REST-like JSON endpoints, generating collection and item routes and handling serialization and responses with convention over configuration. The design intent is 'entity as resource' with minimal boilerplate. It is a historical reference, not a usable dependency.
- Is outlandish/rest-bundle maintained or safe for production?
- No. The repository is archived, has had no release since 2014, and has no security response or issue triage. Auto-exposing entities also inverts safe defaults for authorization and field-level filtering. Do not put it in a production path.
- What is the Laravel equivalent of outlandish/rest-bundle?
- Build the capability natively with Route::apiResource for resourceful routes, API Resources for response shaping, Form Requests for validation, and policies or gates for authorization over Eloquent models. On Symfony, API Platform is the maintained successor pattern for attribute-driven resource exposure. This bundle is not a viable option on either stack.
- Does outlandish/rest-bundle work with Eloquent?
- No. Its central premise is Doctrine entity introspection, which does not translate to Eloquent models. There is no Eloquent adapter, and the Doctrine metadata APIs it relies on have changed substantially in Doctrine ORM 3.x.
- Can I still use outlandish/rest-bundle in a legacy Symfony 2 app?
- Realistically no, not as a supported dependency. It is archived with zero dependents and no maintainer, so any use means owning a fork and patching it indefinitely. That is a migration or removal conversation, not an adoption.
- How do I migrate away from outlandish/rest-bundle?
- Extract the endpoint conventions and contracts rather than the code: list the collection and item routes, HTTP verb mapping, pagination, and response shapes. Then reimplement those contracts on a maintained stack such as Laravel controllers with API Resources, or Symfony with API Platform. Keep the API surface stable while replacing the implementation.
- What are the best alternatives to outlandish/rest-bundle for a Laravel API?
- For Laravel, native resourceful controllers plus API Resources, Form Requests, and policies cover most CRUD APIs over Eloquent. For Symfony, API Platform is the maintained successor pattern. For generic CRUD over Doctrine, a thin custom controller layer over repositories is safer than reviving an abandoned bundle.