Weave Code
Rox Laravel Package
rollout/rox
rollout/rox is a Laravel package for managing feature rollouts and toggles. It helps you enable or disable features for specific users, segments, or rollout percentages, keeping release control in configuration and code.
Rox SDK for PHP
Frequently asked questions about Rox
- Is rollout/rox a Laravel package or a standalone PHP SDK?
- rollout/rox is the vendor PHP client SDK for the Rox/CloudBees Rollout feature-flag and remote-configuration service, not a native Laravel package. It ships with no service provider, no facade, no publishable config file, and no Blade or Vite integration. You are expected to register it yourself in a service provider and call it through an adapter you own rather than statically from controllers and jobs.
- How do I install and configure rollout/rox in a Laravel application?
- Install it with Composer, then pull your environment key and any related credentials from config or environment variables. Bind the SDK as a singleton in a dedicated service provider and add middleware that seeds the per-request user or entity context before any flag evaluation happens. Because there is no first-party Laravel integration, keep the SDK behind a small wrapper class or container-bound contract so application code never touches the vendor API directly.
- Does rollout/rox support percentage rollouts and user targeting?
- Yes. The SDK evaluates flags synchronously against a locally cached flag set using the entity context you register, so percentage-based gradual rollouts and per-user or per-segment targeting are both part of its core model. The rules are defined in the Rox/CloudBees service rather than in PHP code, which is what lets you change exposure without redeploying. Note that the fluent flag-definition API described in some summaries lives in other Rox SDKs, so confirm the exact surface in the PHP client before designing around it.
- Which Laravel and PHP versions does rollout/rox support?
- The SDK is framework-agnostic PHP, so it will generally install into Laravel 9, 10, or 11 as long as the package's PHP constraint matches your pinned platform minor. There is no official Laravel support matrix, so verify the constraint in composer.json before committing. Given the single release and low maintenance signal, pin an exact version rather than a caret range and add the package to your SBOM and license-scanning gate.
- Is rollout/rox safe to use with Laravel Octane, Swoole, or queue workers?
- This is the highest-risk part of the integration. Under classic PHP-FPM the request lifecycle maps cleanly onto the SDK's boot-and-register-entity model, but in long-lived workers the current entity is mutable global state that can leak one user's targeting decisions to another request. You must reset the entity context per request in middleware, set and restore it explicitly in queue jobs, and cover the reset behaviour with a regression test before shipping.
- What license does rollout/rox use, and can I ship it to production?
- The repository metadata reports NOASSERTION, meaning GitHub could not identify an SPDX license for the project. That is a legal blocker rather than a technical one, and it should be resolved in writing with the vendor before the package reaches production. Start that conversation on day one, because no amount of clean integration work compensates for an unclear license.
- Is rollout/rox still maintained now that Rollout is part of CloudBees?
- Rollout was absorbed into CloudBees and the Rox-branded SDKs are effectively in maintenance while the portfolio consolidates around CloudBees Feature Management. The PHP repository shows a single release in January 2024, zero stars, and zero dependents, which means little public production validation. Treat a forced migration within 12 to 24 months as a realistic scenario and budget for the exit cost up front.
- What happens if flag evaluation fails or the network is unreachable?
- Flag evaluation depends on a flag payload that is fetched and cached locally, so cold starts, cache misses, and partial connectivity all affect behaviour. You need explicit tests for those paths and an agreed fail-open or fail-closed policy that your application owns, not the SDK. Also measure the p99 latency the lookup adds to a request before rolling it out broadly.
- Does rollout/rox include testing helpers for toggling flags predictably?
- The SDK's local flag-set model means you can seed or override values in tests, but there is no Laravel testing trait equivalent to what first-party tooling provides. The practical approach is to bind a fake implementation of your own flag contract in the test container and assert against that. Keeping the vendor SDK behind an interface makes this trivial and also isolates you from a future migration.
- What are the alternatives to rollout/rox for feature flags in Laravel?
- Laravel Pennant is the first-party, free option and is already available in the framework, which makes it the obvious choice if you only need static on/off flags. If you need hosted experimentation, segmentation, and a management UI, look at LaunchDarkly, Unleash, or Flagsmith, all of which have active PHP clients. Compare those against Rox on license clarity, Octane safety, and long-term vendor roadmap before committing.
Weaver
How can I help you explore Laravel packages today?