Download the PHP package lukewaite/laravel-queue-aws-batch without Composer
On this page you can find all versions of the php package lukewaite/laravel-queue-aws-batch. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
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 laravel-queue-aws-batch
Laravel Queue for AWS Batch
Supported Versions
| Laravel Version | Package Tag | Supported |
|---|---|---|
| 8.x | unreleased | yes |
| 5.4.x | 2.0.x | no |
| 5.3.x | 1.0.x | no |
| 5.2.x | 1.0.x | no |
| 5.1.x | 1.0.x | no |
Installation
See the table above for package version information, and change the version below accordingly.
Using composer, run:
composer require lukewaite/laravel-queue-aws-batch ~2.0Usage
-
Your Laravel application will need to be dockerized and pushed into a container registry of your choice. The
ENTRYPOINTshould be set toartisan. - Add a new queue to your
config/queues.phpconfig file'sconnectionsarray:
This queue transport depends on being able to write it's queue jobs to a database queue. In this example, it writes it's
jobs to the jobs table. You'll need to use the artisan queue:table to create a migration to create this table.
-
Create an AWS Batch job queue with the same name as the
queueconfig setting. This is where the Batch connector will push your jobs into Batch. In this case, my queue name would befirst-run-job-queue. - Create a AWS Batch job definition for each queue you define that looks something like this:
Here, you configure your container to start, run the queue:work-batch command (assuming artisan is your entrypoint)
and pass in the name of the queue, first-run-job-queue as well as the Ref::jobId param, which is passed in when
the Batch connector creates the job.
It is important that you configure a retryStrategy with more "attempts" than you are running tries if you provide that
argument. Otherwise, Batch will not retry your job if it fails. Laravel 5.1 does not write to the failed job queue until
the next run after tries has been exceeded by jobs failing. Newer versions will write to the queue in the same run, so
this requirement can be relaxed later.
- Add the Service Provider to your application:
- In
config/app.phpadd to theprovidersarray:LukeWaite\LaravelQueueAwsBatch\BatchQueueServiceProvider::class
- In
Limitations
Delayed Jobs
AWS Batch has no method to delay a job and as it's our runner, we don't have an easy work around. If you require delayed jobs for your use case, at this point my recommendation would be to use a regular DB queue, and to fire a job into it which will fire your batch job at the correct time.
