Download the PHP package neophp/queue-package without Composer
On this page you can find all versions of the php package neophp/queue-package. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download neophp/queue-package
More information about neophp/queue-package
Files in neophp/queue-package
Package queue-package
Short Description Simple database-backed job queue for NeoPHP, processed via a batch worker command
License MIT
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package queue-package
Queue Package
A simple, database-backed job queue for NeoPHP. Push jobs, process them in batches via a worker command triggered by a system cron — no long-running process, no external dependency like Redis or a message broker.
Structure
How it works
Jobs are stored as rows in neo_queue_jobs — no long-running worker
process, no Supervisor/systemd setup required. Instead, a system cron
calls queue:work on a schedule (typically every minute); each run
picks up a batch of due jobs, processes them, and exits.
If a job throws, it's automatically retried with exponential backoff
(1 minute, then 5 minutes) up to 3 attempts total, after which it's
marked permanently failed and left for manual inspection.
Installation
Register it in the project's Config/app.config.php:
Run the migration:
Creating a job
Generates src/MyProject/App/Job/SendWelcomeEmailJob.php:
Keep job constructor parameters simple (scalars, IDs) rather than
storing whole entity objects — a job may sit in the queue for a while
before being processed, so a stale entity reference (deleted row,
detached object) is a real risk. Re-fetch what you need inside
handle().
Pushing a job
Processing jobs
| Option | Default | Purpose |
|---|---|---|
--queue |
default |
Which queue to process |
--limit |
50 |
Maximum jobs processed in this run |
Each invocation processes what's currently due, then exits — safe to
run every minute via cron even if the previous run is still finishing,
since each job is marked processing immediately and won't be picked
up twice.
Retrying permanently failed jobs
Resets every job in the failed state back to pending with a fresh
attempt count, so the next queue:work run picks them up again. There
is currently no way to inspect why a job failed other than querying
neo_queue_jobs.last_error directly — no CLI/UI listing is provided in
this version.
QueueManager API
| Method | Purpose |
|---|---|
push(JobInterface $job, string $queue = 'default', int $priority = 0): void |
Enqueue a job |
work(string $queue = 'default', int $limit = 50): array{processed, succeeded, failed} |
Process a batch of due jobs |
retryFailed(): int |
Reset all failed jobs to pending, returns count |
stats(): array{pending, processing, done, failed} |
Current job counts by status |
Known limitations
- No true concurrency protection. If two
queue:workprocesses run at the exact same moment (e.g. a slow run overlapping with the next cron tick), there's a small race window between reading due jobs and marking themprocessing— acceptable for most use cases, but not suitable for jobs that absolutely cannot run twice without a database-level lock, which this package does not implement. - Jobs are serialized with PHP's native
serialize(). If you change a job class's constructor signature or namespace after jobs referencing it are already queued, those pending jobs will fail to unserialize. Keep queues empty during deployments that rename or restructure job classes. - No priority across queues — priority only orders jobs within the same queue name, not between different queues.
- No dashboard/UI — inspect job status directly via SQL or build your
own admin page using
QueueJobRepository.
License
MIT
