title: Setting up rake-pipeline for use with handlebars alongside Google App Engine
body: <p>So here's what I'm attempting to do. I'm building an ember.js application, with a java backend running on GAE.</p>
  
  <p>I'm using handlebars, but I want them divided up into separate files, not just all pasted into the index.html.</p>
  
  <p>Via the ember.js irc I was turned on to <a href="http://rubydoc.info/github/livingsocial/rake-pipeline/master/file/README.yard" rel="nofollow noreferrer">rake-pipeline</a> along with <a href="https://github.com/wycats/minispade" rel="nofollow noreferrer">minispade</a></p>
  
  <p>Along with the <a href="http://rubydoc.info/github/wycats/rake-pipeline-web-filters/master/file/README.yard" rel="nofollow noreferrer">web filters</a> and a custom <a href="https://gist.github.com/1477124" rel="nofollow noreferrer">handlebars filter</a> I started building the assetfile. I don't know Ruby, or gem files, etc.</p>
  
  <p>So I'm trying to figure out the best way to be able to compile my coffeescript/handlebars files on the fly, minispade them, but keep the individual files accessible while in dev mode so I can debug them. What makes that hard is that the rake pipeline is running on a different port than GAE. So I'm not sure exactly how to handle this. Do I make my index file in GAE point to individual files at the 9292 port (rakep) during development, but in production mode point to the fully concatenated version? I'm not sure.</p>
  
  <p>So I was attempting to do that here: <a href="https://gist.github.com/1495740" rel="nofollow noreferrer">https://gist.github.com/1495740</a>  by having only one section that was triggered by the 'build' flag. Not even sure if that works that way.</p>
  
  <p>I know there's a lot of confusion here. Apologies, like I said I'm not even remotely familiar with the Ruby style of doing things.</p>