Laravel features

Fluxo inspects the active composer.lock rather than assuming packages from the selected site label. Laravel feature controls appear only when the framework and relevant packages are actually installed in the active application.

After adding a Composer package, deploy successfully and refresh the site Overview so Fluxo can inspect the new lockfile.

Scheduler

The Scheduler control becomes available when Laravel is detected. Enabling it creates a once-per-minute cron entry that runs the version-specific PHP executable against the active artisan schedule:run command.

Define actual schedules inside the Laravel application. Fluxo's cron only wakes Laravel's scheduler every minute.

Maintenance mode

Maintenance mode uses the active Laravel application's artisan down and artisan up behavior. Use it for changes that cannot safely run while requests are served.

Maintenance mode is application state, not a substitute for a failed deployment rollback. Confirm privileged bypass or retry behavior according to the Laravel version in use.

Queue Worker

Queue Worker appears whenever Laravel is detected. Enabling the toggle opens a configuration form for the queue connection, comma-separated queue priority, process count, retry behavior, job timeout, backoff, memory limit, maximum process lifetime, and maintenance-mode behavior.

After activation, the Laravel Features card keeps only the enable/disable toggle. To change an active worker's settings, open Site > Processes > Background Processes, use the managed Queue Worker's action menu, and select Configure worker.

Fluxo writes the selected connection to QUEUE_CONNECTION, clears Laravel's configuration cache, and creates a managed systemd process group. The configured process count is the number of independent queue:work processes Fluxo starts. Successful deployments and release rollbacks run artisan queue:restart, allowing in-flight jobs to finish before workers load the active code.

Custom queue daemons remain untouched and are reported as a warning in the form. Avoid running both a custom process and the managed worker against the same queues unless that extra concurrency is deliberate.

Queue Worker and Horizon are mutually exclusive. Enabling Horizon first validates the installed package and Redis connection, then removes the managed Queue Worker and preserves its settings. Fluxo automatically restores the worker if Horizon activation fails. Disabling Horizon later does not automatically re-enable the worker.

Horizon

Horizon appears when laravel/horizon is present in the active lockfile. It requires QUEUE_CONNECTION=redis and a working Redis connection. Enabling it creates a managed Horizon process. Fluxo terminates Horizon after successful managed deployments so Laravel's process monitor starts workers on the new code.

Configure queues, balancing, timeouts, and supervisors in the application before enabling the service.

Nightwatch

Nightwatch appears when the Laravel Nightwatch package is detected. Enabling it creates the required background agent and assigns an available internal port where needed.

Package configuration and credentials remain the application's responsibility.

Octane

Octane appears when laravel/octane is detected and the site uses standard deployment. Enabling it creates the Octane server process and Nginx proxy configuration on a unique internal port.

Fluxo reloads Octane after successful application deployment. Disable Octane before switching the site to zero-downtime deployment.

Long-lived workers

Queue Workers, Horizon, and Octane keep application state in memory. Ensure services restart or reload after code and configuration changes, and design application code to release request-specific resources.

Feature does not appear

Check that:

1. The active release contains composer.lock.
2. The package was installed into that release.
3. The package name and version are recorded in the lockfile.
4. The latest deployment succeeded.
5. Octane is not hidden by zero-downtime mode.