Apps Artificial Intelligence CSS DevOps Go JavaScript Laravel Linux MongoDB MySQL PHP Python Rust Svelte Vue

Running Laravel Queues on cPanel with Cron Jobs

2 min read .
Published on
Running Laravel Queues on cPanel with Cron Jobs

Laravel queues are useful for work that should not block an HTTP request, such as sending email, generating reports, importing data, or processing files. On a VPS, a process supervisor is usually the best way to keep long-running queue workers alive. Shared cPanel hosting often does not provide that option, so a cron-driven worker can be a practical fallback.

This pattern starts a worker periodically and tells it to exit once the queue becomes empty.

1. Schedule the Queue Worker

In current Laravel applications, scheduled tasks are commonly defined in routes/console.php with the Schedule facade:

use Illuminate\Support\Facades\Schedule;

Schedule::command('queue:work --stop-when-empty')
    ->everyMinute()
    ->withoutOverlapping();

Older Laravel applications may define the same schedule in app/Console/Kernel.php.

The options mean:

  • queue:work starts a queue worker.
  • --stop-when-empty exits after the currently available jobs have been processed.
  • everyMinute() lets the Laravel scheduler consider the command every minute.
  • withoutOverlapping() prevents the scheduler from starting a second copy while the previous scheduled invocation is still considered active.

For long-running jobs, configure suitable worker timeouts, retry policies, and the withoutOverlapping() lock expiration so a crashed process does not leave an unexpectedly long-lived lock.

2. Add a cPanel Cron Job

Open cPanel → Cron Jobs and add a cron entry that runs Laravel’s scheduler once per minute. The PHP executable depends on the hosting provider and selected PHP version.

For example:

* * * * * /usr/local/bin/ea-php84 /home/{account_name}/live/artisan schedule:run

Another server may expose a different binary such as ea-php83, php, or a versioned path. Confirm the exact PHP CLI path in your hosting environment.

Replace:

  • {account_name} with the cPanel account name.
  • live with the Laravel project directory.
  • ea-php84 with the PHP CLI binary used by the application.

It is also a good idea to change into the project directory explicitly when the hosting environment requires it:

* * * * * cd /home/{account_name}/live && /usr/local/bin/ea-php84 artisan schedule:run >> /dev/null 2>&1

Only discard output after you have a separate logging and monitoring strategy; during setup, keeping cron errors visible is useful.

3. How the Flow Works

  1. Cron runs php artisan schedule:run every minute.
  2. Laravel evaluates the application schedule.
  3. When due, the scheduler launches queue:work --stop-when-empty.
  4. The worker processes available jobs and exits after the queue is empty.
  5. A later cron invocation starts another worker when needed.

This is not equivalent to a continuously running worker—new jobs may wait until the next cron cycle—but it can be sufficient for shared-hosting workloads that tolerate that delay.

4. Practical Tips

A database-backed queue is often available on shared hosting:

QUEUE_CONNECTION=database

Create the required queue table using the commands appropriate for your Laravel version, then migrate the database. In versions that provide the command, that may look like:

php artisan make:queue-table
php artisan migrate

Other useful operational commands include:

php artisan queue:failed
php artisan queue:retry {id}

Also consider:

  • Keeping queued jobs small and idempotent so retries are safe.
  • Configuring failed-job storage and monitoring it.
  • Setting --tries, --timeout, and queue names when the defaults do not fit your workload.
  • Using separate cron entries for separate Laravel projects.
  • Moving to a persistent process manager, container platform, or managed queue worker when job volume or latency requirements grow.

Conclusion

On cPanel hosting without a process supervisor, running schedule:run every minute and scheduling queue:work --stop-when-empty can keep Laravel queues moving with minimal infrastructure. It is a useful shared-hosting compromise, but a continuously supervised worker remains the better option when low latency, throughput, and worker observability matter.

Laravel Queue

Related Posts

Automatically Encrypting Eloquent Model Attributes
Published on
Automatically Encrypting Eloquent Model Attributes
Applications often store fields that deserve additional protection at rest. Laravel can encrypt selected Eloquent attributes before they are written to the database and decrypt them automatically when they are read. For modern Laravel applications, the built-in encrypted cast is preferable to overriding Eloquent’s magic __get() and __set() methods. It integrates with the model casting system and avoids interfering with Eloquent internals. Basic Implementation Define encrypted attributes in the model’s casts:
Laravel Security Encryption
Building a Live Search Page in Filament PHP
Updated on
Building a Live Search Page in Filament PHP
Real-time search can make an admin dashboard much easier to use. Filament is built on Livewire, so a custom resource page can react to search input without writing a separate frontend application. This example adds a live-search page to a PostResource. 1. Generate a Custom Page Generate a custom page inside the resource: Copy php artisan make:filament-page SearchPost --resource=PostResource --type=custom The exact generated path can vary by Filament version and panel structure, so check the files created by the command.
Laravel Filament
Building a Nested Category API in Laravel 11: A Practical Guide
Updated on
Building a Nested Category API in Laravel 11: A Practical Guide
Nested categories are common in e-commerce platforms, CMS applications, documentation systems, and other products that need hierarchical navigation. In Laravel, a self-referencing Eloquent relationship can model a category that belongs to a parent and has any number of children. This Laravel 11 example builds a small API for creating and reading category trees. 1. Create the Laravel Project Copy composer create-project --prefer-dist laravel/laravel laravel-nested-categories cd laravel-nested-categories php artisan serve 2. Create the Category Model and Migration Copy php artisan make:model Category -m Define the table in the generated migration:
Laravel
Building a Simple CRUD Application in Laravel: A Practical Guide
Updated on
Building a Simple CRUD Application in Laravel: A Practical Guide
Building a CRUD application is one of the best ways to learn the core pieces of Laravel. In this guide, we will create a simple Post resource that supports Create, Read, Update, and Delete operations using Eloquent, resource routes, validation, and Blade views. 1. Create the Laravel Project Make sure Composer and a supported PHP version are installed, then run: Copy composer create-project --prefer-dist laravel/laravel laravel-crud cd laravel-crud php artisan serve The development server is normally available at http://localhost:8000.
Laravel CRUD
Data Validation in Laravel: A Complete Developer Guide
Updated on
Data Validation in Laravel: A Complete Developer Guide
Validation is an important boundary in web applications. It ensures incoming data has the shape and constraints your application expects before that data reaches business logic or persistence. Laravel provides several validation APIs, from quick controller validation to reusable Form Request classes and custom rules. 1. Basic Validation For small request handlers, call validate() on the request: Copy use Illuminate\Http\Request; public function store(Request $request) { $validatedData = $request->validate([ 'name' => ['required', 'string', 'max:255'], 'email' => ['required', 'email', 'unique:users,email'], 'password' => ['required', 'string', 'min:8', 'confirmed'], ]); // Use $validatedData rather than the entire request payload. } For a normal browser request, Laravel redirects back with validation errors in the session. For requests expecting JSON, Laravel returns a validation error response, normally with HTTP status 422.
Laravel Validation
Understanding HTTP Status Codes in Laravel: A Developer's Guide
Updated on
Understanding HTTP Status Codes in Laravel: A Developer's Guide
HTTP status codes tell clients whether a request succeeded, failed, requires authentication, or encountered another condition. Choosing the right status code makes Laravel APIs easier to consume and helps clients implement predictable error handling. 200: OK Use 200 OK when a request succeeds and the response includes a representation or other useful content. Common cases: A successful GET request that returns data. A successful update that returns the updated resource. A successful action endpoint that returns a result. 201: Created Use 201 Created after successfully creating a new resource, usually from a POST request.
Laravel
chevron-up