title: Adding foreman on passenger
body: <p>So far I had a simple application that only required the classic <code>rails server</code> to boot.</p>
  
  <p>I have recently added the <code>react_on_rails</code> gem and it requires to boot a nodejs server to handle webpack and javascript stuff. </p>
  
  <p>So I understand I need this <code>foreman</code> gem that is capable of managing several processes. So far so good, but then I'm still having a few problems understanding and deploying this enhanced app to my production environment (Phusion Passenger on Apache/Nginx)</p>
  
  <p>So several questions :</p>
  
  <ul>
  <li>Does passenger handle the transition from <code>rails s</code> to <code>foreman start -f Procfile.dev</code> automatically ?</li>
  <li>If <code>no</code> then where do I setup things so passenger works ?</li>
  <li>Side question : almost all google results refer to <code>puppet</code> when looking for <code>foreman on passenger</code>. Anyone could explain what <code>puppet</code> does in 1 line and if I really need it in production ? So far everythings runs smoothly on localhost with the <code>foreman start -f Procfile.dev</code> command so I don't know where this is coming from...</li>
  </ul>
  
  <p>I am deploying my application to the Amazon Cloud using Capistrano, and I was expecting to have the rails + nodejs setup on every autoscaled instance (and Passenger would graciously handle all that). Am I thinking wrong ?</p>