Website & Admin Panel

Cron & Queue Workers

Two background processes keep the platform running smoothly: the scheduler (timed tasks) and the queue worker (jobs like push notifications and emails). Set up both.

1. The scheduler (cron)

Add a single cron entry that runs every minute. Laravel decides what actually needs to run.

Find the right binary and the app's real path first:

cd /path/to/your/app && pwd          # the exact app path
ls /usr/bin/php8* /opt/alt/php8*/usr/bin/php 2>/dev/null   # available binaries
which php                                # what plain "php" would give cron

Then build the entry from those two values:

# shared hosting (CloudLinux / Hostinger layout)
* * * * * cd /home/USER/domains/YOURDOMAIN/public_html/shop && /opt/alt/php84/usr/bin/php artisan schedule:run >> storage/logs/cron.log 2>&1

# cPanel with a system PHP
* * * * * cd /home/USER/bringo && /usr/local/bin/php artisan schedule:run >> storage/logs/cron.log 2>&1

# VPS
* * * * * cd /var/www/bringo && /usr/bin/php artisan schedule:run >> storage/logs/cron.log 2>&1

Verify it by hand before trusting cron — run the exact command from the entry, with the full binary path:

cd /path/to/your/app && /opt/alt/php84/usr/bin/php artisan schedule:run

You should see either a list of tasks that ran, or "No scheduled commands are ready to run." Anything else — a PHP version error, a missing vendor/ — would have been invisible inside cron.

On cPanel/hPanel, add the entry through Cron Jobs in the panel rather than crontab -e.

What the scheduler runs

2. Triggering tasks over HTTP (no shell access needed)

Most scheduled tasks can also be fired through a URL — useful on shared hosting without cron access, with external cron services (cron-job.org, EasyCron…), or for testing a task right now. The single /cron/run URL runs the whole schedule, so it covers every task including the ones with no individual URL.

Set the secret key

Add a long random secret to your .env, then refresh the config cache:

CRON_SECRET=paste-a-long-random-string-here

php artisan config:clear && php artisan config:cache

URL format

https://your-domain.com/cron/run/{task}?key=CRON_SECRET

The most important URL — run everything that is due (point your external cron service at this one, every minute or every 5 minutes):

https://your-domain.com/cron/run?key=CRON_SECRET

All task URLs

Replace your-domain.com and CRON_SECRET with your values. Prefix each with https://your-domain.com/cron/run/:

Example — settle seasonal cashback immediately instead of waiting for the hourly run:

https://your-domain.com/cron/run/cashback:process-seasonal?key=CRON_SECRET

3. The queue worker

Jobs (push notifications, emails) are pushed to a queue and processed by a worker.

On a VPS — use Supervisor (recommended)

sudo apt install -y supervisor

Create /etc/supervisor/conf.d/bringo-worker.conf:

[program:bringo-worker]
process_name=%(program_name)s_%(process_num)02d
command=php /var/www/bringo/artisan queue:work database --sleep=3 --tries=3 --max-time=3600
autostart=true
autorestart=true
user=www-data
numprocs=1
redirect_stderr=true
stdout_logfile=/var/www/bringo/storage/logs/worker.log
stopwaitsecs=3600

sudo supervisorctl reread
sudo supervisorctl update
sudo supervisorctl start bringo-worker:*

On shared hosting — cron fallback

If you can't run a permanent process, add a second cron job that drains the queue periodically. The same rule applies — full path to PHP, real app path:

* * * * * cd /home/USER/domains/YOURDOMAIN/public_html/shop && /opt/alt/php84/usr/bin/php artisan queue:work --stop-when-empty >> storage/logs/worker.log 2>&1

--stop-when-empty makes the worker exit once the queue is drained, so the next minute's run starts cleanly instead of stacking up processes. If your host limits how long a process may live, add --max-time=50 so it always finishes inside the minute.