Weave Code
Symfony Rollout Rox Laravel Package
krak/symfony-rollout-rox
Symfony bundle for integrating Rox feature rollout management into PHP applications. Provides simple configuration and service wiring so you can control feature flags, target audiences, and gradual releases with minimal setup and no boilerplate. Ideal for teams adopting progressive delivery.
Rollout ROX Integration with Symfony
Frequently asked questions about Symfony Rollout Rox
- Does krak/symfony-rollout-rox work with Laravel?
- No. krak/symfony-rollout-rox is a Symfony bundle that relies on Symfony's kernel, DI extension, and compiler passes, so it does not boot in a Laravel application. Laravel has no equivalent of Kernel::registerBundles() or Extension::load(), which are central to how this package wires the Rox client. You should treat it as a reference implementation to port, not a Composer package to install in Laravel.
- How do I install krak/symfony-rollout-rox in a Laravel project?
- You cannot install it as a working Laravel integration. Composer may resolve the package, but without a Laravel service provider and config binding the Rox client will not be registered in Laravel's container. The practical path is to require the underlying Rollout Rox PHP SDK directly and write your own Laravel service provider, facade, and config file.
- Can I use Rox feature flags in Laravel without the Symfony bundle?
- Yes, if the Rox PHP SDK is framework-agnostic enough for your needs. Depend on the SDK directly and wrap it in an Illuminate\Support\ServiceProvider, with mergeConfigFrom() for API key and environment settings and a singleton binding for the client. Audit the SDK first for global static initialization and PSR-18/PSR-16 transport and cache support, because those details determine how cleanly it fits Laravel.
- What Laravel versions does krak/symfony-rollout-rox support?
- None officially. The package is built for Symfony and declares no Laravel service provider, facade, or version constraints for the Laravel framework. Any Laravel version support would come from a port you write or from a different package. Check the underlying Rox PHP SDK's PHP version requirements before assuming compatibility with your Laravel app.
- How do I configure the Rox API key and environment in Laravel?
- The Symfony bundle exposes these through bundle settings in config, but Laravel will not read that config tree. In a Laravel port you would create config/rox.php, load it with mergeConfigFrom(), and publish it with publishes() so each environment can set its own API key, environment, and container options. Then bind the configured Rox client as a singleton in a service provider.
- Is krak/symfony-rollout-rox safe for production Laravel applications?
- It is not a production-ready Laravel package because it does not integrate with Laravel at all. Even in Symfony, v0.1.0 is a pre-1.0 initial release with no downstream validation or production evidence, and the metadata shows a 2020 last-release date that conflicts with the initial-release label. The vendor risk also sits with CloudBees Rox, so SDK lifecycle and hosted-service terms are outside the maintainer's control.
- How do I test feature flags with krak/symfony-rollout-rox in Laravel?
- You cannot test the Symfony bundle directly inside Laravel's container. For a Laravel port, define a small flag-check interface, bind a fake implementation in tests, and assert the branches your controllers, jobs, and Blade views take. If you use the Rox SDK directly, wrap it behind that interface so tests never need a network call or a live Rox container.
- What are the best alternatives to krak/symfony-rollout-rox for Laravel feature flags?
- Laravel Pennant is the first-party option for simple feature flags and A/B-style scopes. For hosted flag management you can evaluate LaunchDarkly, Unleash, Flagsmith, or CloudBees Rox through their PHP SDKs and thin Laravel service providers. If you specifically need Rox, depend on the Rox PHP SDK and write the Laravel binding yourself rather than using this Symfony bundle.
- How does lazy loading of Rox containers work with Laravel Octane or queue workers?
- The bundle's lazy loading is Symfony container lazy instantiation, not a Laravel feature. In a long-lived Laravel process such as Octane or a queue worker, you must decide when the Rox container is refreshed and whether flag state can go stale between requests. A port should make refresh explicit and avoid assuming per-request initialization that Symfony's kernel would normally provide.
- Is krak/symfony-rollout-rox maintained, and what risks should I check?
- Treat maintenance as unproven. The package is at v0.1.0, has no dependents or production evidence, and has a metadata conflict between a 2020 last-release date and an initial-release description, which suggests a version reset, fork, or republish. Before relying on it, check git tag dates and history, confirm the Rox PHP SDK's support status under CloudBees, and decide whether you own the Laravel port.
Weaver
How can I help you explore Laravel packages today?