PHPackages biigle/laravel-remote-queue - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. [Queues & Workers](/categories/queues) 4. / 5. biigle/laravel-remote-queue AbandonedArchivedLibrary[Queues & Workers](/categories/queues) biigle/laravel-remote-queue =========================== Submit jobs to and receive jobs from other Laravel or Lumen instances. v2.3.2(6y ago)43.0k2MITPHP Since Oct 31Pushed 5y ago2 watchersCompare [ Source](https://github.com/biigle/laravel-remote-queue)[ Packagist](https://packagist.org/packages/biigle/laravel-remote-queue)[ RSS](/packages/biigle-laravel-remote-queue/feed)WikiDiscussions master Synced 1mo ago READMEChangelog (10)Dependencies (8)Versions (18)Used By (0) Remote Queue ============ [](#remote-queue) Submit jobs to and receive jobs from other Laravel or Lumen instances. [![Build Status](https://camo.githubusercontent.com/0e9741b59bc53128ce85e417ab2f291b1fcce7bd52bc8fda09311736f48d9933/68747470733a2f2f7472617669732d63692e6f72672f626969676c652f6c61726176656c2d72656d6f74652d71756575652e7376673f6272616e63683d76352e372e37)](https://travis-ci.org/biigle/laravel-remote-queue) Installation ------------ [](#installation) ``` composer require biigle/laravel-remote-queue ``` ### Laravel [](#laravel) The service provider is auto-discovered by Laravel. ### Lumen [](#lumen) Add `$app->register(Biigle\RemoteQueue\RemoteQueueServiceProvider::class);` to `bootstrap/app.php`. Usage ----- [](#usage) This package can be used to submit queued jobs to another Laravel or Lumen application, receive jobs from another application or both. ### Receive jobs [](#receive-jobs) By default, this package does not allow receiving of jobs from another application. To allow this, set the `remote-queue.listen` configuration to `true`. Tokens are used to authenticate incoming requests. A token is just some long random string in this case. Configure `remote-queue.accept-tokens` with all tokens that are accepted. All received jobs which are successfully authenticated are pushed to a "regular" queue of this application and processed by the queue worker. **Important:** Make sure that the job class exists in both the submitting and receiving application. ### Submit jobs [](#submit-jobs) Jobs pushed to the remote queue are transmitted via HTTP and processed on another application. To use the remote queue, configure a queue connection in the `queue.connections` config to use the `remote` driver. Example: ``` [ 'driver' => 'remote', // Default queue of the remote host to push jobs to. 'queue' => 'default', // The remote queue API endpoint of the remote host. Don't forget the trailing slash! 'url' => 'http://192.168.100.100/api/v1/remote-queue/', // Token to use for authentication on the remote host. 'token' => 'IoO2l7UKZfso5zQloF2XvAShEbAR5a9M8u+WBfg0HgI=', // Optional additional request options for the GuzzleHttp client. 'request_options' => [], ] ``` You can now dispatch jobs to the remote queue connection just like any other connection. ``` use App\Jobs\MyJob; MyJob::dispatch($data)->onConnection('remote'); ``` ### Submit/Response Pattern [](#submitresponse-pattern) We developed this package to be able to process jobs on a remote machine with GPU. To return the computed results, we applied what we call the "submit/response" pattern. In this pattern, this package is installed on both Laravel/Lumen instances (let's call them A and B). In instance A, the remote queue is configured to push jobs to instance B (the one with the GPU). In instance B, the remote queue is configured to push jobs to instance A. New GPU jobs are submitted from instance A to the remote queue on instance B. Once the results are computed, they are returned as a "response job" to the remote queue on instance A where the results can be further processed. Configuration ------------- [](#configuration) You can override any of these configuration options of the `remote-queue` config either directly or via environment variables: ### remote-queue.listen [](#remote-queuelisten) Default: `false`Environment: `REMOTE_QUEUE_LISTEN` Accept and process jobs sent to this application instance. ### remote-queue.endpoint [](#remote-queueendpoint) Default: `api/v1/remote-queue`Environment: `REMOTE_QUEUE_ENDPOINT` API endpoint to receive new jobs. ### remote-queue.connection [](#remote-queueconnection) Default: `null`Environment: `REMOTE_QUEUE_CONNECTION` Use this queue connection to process received jobs. If `null`, the default connection is used. ### remote-queue.accept\_tokens [](#remote-queueaccept_tokens) Default: `[]`Environment: `REMOTE_QUEUE_ACCEPT_TOKENS` Accept jobs only if they provide one of these tokens. Specify tokens as comma separated list if you use the environment variable. One way to generate tokens is this command: `head -c 32 /dev/urandom | base64`. ### remote-queue.accept\_ips [](#remote-queueaccept_ips) Default: `[]` Accept requests only from the IP addresses of this whitelist. Leave empty to accept jobs from all IPs. ### remote-queue.accept\_jobs [](#remote-queueaccept_jobs) Default: `[]` Accept only jobs of this whitelist of class names. Leave empty to accept all job classes. ### Health Score 34 — LowBetter than 77% of packages Maintenance20 Infrequent updates — may be unmaintained Popularity22 Limited adoption so far Community11 Small or concentrated contributor base Maturity69 Established project with proven stability Bus Factor1 Top contributor holds 98% of commits — single point of failure How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** — Project age, version count, PHP version support, and release stability. ### Release Activity Cadence Every ~34 days Recently: every ~117 days Total 16 Last Release 2230d ago Major Versions v1.0.0 → v2.0.02018-10-31 v0.2.2 → v1.1.02018-11-27 v1.1.0 → v2.1.02018-11-27 v1.1.1 → v2.1.12018-12-14 v1.2.0 → v2.2.02018-12-18 ### Community Maintainers ![](https://avatars.githubusercontent.com/u/2457311?v=4)[Martin Zurowietz](/maintainers/mzur)[@mzur](https://github.com/mzur) --- Top Contributors [![mzur](https://avatars.githubusercontent.com/u/2457311?v=4)](https://github.com/mzur "mzur (49 commits)")[![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?v=4)](https://github.com/dependabot[bot] "dependabot[bot] (1 commits)") --- Tags laravellumenqueueremote ### Code Quality TestsPHPUnit ### Embed Badge ![Health badge](/badges/biigle-laravel-remote-queue/health.svg) ``` [![Health](https://phpackages.com/badges/biigle-laravel-remote-queue/health.svg)](https://phpackages.com/packages/biigle-laravel-remote-queue) ``` ### Alternatives [laravel/boost Laravel Boost accelerates AI-assisted development by providing the essential context and structure that AI needs to generate high-quality, Laravel-specific code. 3.4k10.6M272](/packages/laravel-boost)[roots/acorn Framework for Roots WordPress projects built with Laravel components. 9682.1M97](/packages/roots-acorn)[laravel/pulse Laravel Pulse is a real-time application performance monitoring tool and dashboard for your Laravel application. 1.7k12.1M99](/packages/laravel-pulse)[laravel/cashier-paddle Cashier Paddle provides an expressive, fluent interface to Paddle's subscription billing services. 264778.4k3](/packages/laravel-cashier-paddle)[flarum/core Delightfully simple forum software. 211.3M1.9k](/packages/flarum-core)[palpalani/laravel-sqs-queue-json-reader Custom SQS queue reader for Laravel 26109.8k](/packages/palpalani-laravel-sqs-queue-json-reader) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)