title: Running beanstalkd worker on a remote server
body: <p>My stack set-up consists of the following<br><br>
  <b>Machine1</b> - Main Server (Running laravel)<br>
  <b>Machine2</b> - MySql Server for the laravel codebase<br>
  <b>Machine3</b> - Beanstalkd worker
  <br>
  <br>
  I have setup Supervisord on <strong>Machine1</strong> and added the following queue listener</p>
  
  <pre><code>[program:queue1]
  command=php artisan queue:listen --queue=queue1 --tries=2
  ...
  </code></pre>
  
  <p>My laravel queue config file(app/config/queue.php) reads the following</p>
  
  <pre><code>'beanstalkd' =&gt; array(
      'driver' =&gt; 'beanstalkd',
      'host'   =&gt; '--- Machine3 IP ---',
      'queue'  =&gt; 'queue1',
      'ttr'    =&gt; 60,
  ),
  </code></pre>
  
  <p>And I have installed beanstalkd on <strong>Machine3</strong> along with Beanstalk console and can see my tasks being pushed to the queue and executing successfully. However I am not sure if <strong>Machine3</strong> is actually executing them, and the reason for my suspicion is the High CPU usage on the main server as compared to no spikes in CPU usage on <strong>Machine3</strong></p>
  
  <p>I completely shutdown my beanstalkd Server to check if the queue still processes and the outcome was an error reported by laravel indicating it could not connect to the beanstalkd server.</p>
  
  <p>I read somewhere that you need to have your laravel codebase on the beanstalkd server(<strong>Machine3</strong>) too, was that really the way to go?</p>