title: Laravel Queue Worker, RabbitMQ and running jobs generated remotely
body: <p>I'll preface this by admitting slight sleep-deprivation.</p>
  
  <p>The setup is as follows:</p>
  
  <p><strong>API Endpoint (Server A)</strong> receives an incoming call, and adds this to a specific queue on the RabbitMQ Server (Server B).</p>
  
  <p><strong>RabbitMQ (Server B)</strong> is simply a RabbitMQ Queue Server. Nothing more, nothing less.</p>
  
  <p><strong>Laravel Installation (Server C)</strong> is our actual Laravel install, which is meant to look for jobs on specific queues and do things with them.</p>
  
  <p>We have a RabbitMQ package in the Laravel install, which allows the use of the regular Laravel Queue mechanics over a RabbitMQ connection.</p>
  
  <p>The issue I've come across is that we can spawn a worker for a queue - but since we're not generating the jobs passing a <code>$job</code> class (the job content itself is most often a JSON array), the Laravel install has no idea what to do with the job.</p>
  
  <p>So my question revolves mainly around how to approach a scenario like this. I'm thinking that using the Queue-functionality in Laravel won't do what I need it to do. Can you see an approach that I'm missing? Do I really need to spawn a daemon on a non-framework script to handle this?</p>
  
  <p>Your input is much appreciated!</p>