title: Node - Express + Ember + Socket io project file structure for MVC development
body: <p>So i've recently started getting into <strong>node</strong>, and have started working on a few projects using the <strong>Express framework</strong>. I love it - the syntax really appeals to me, being an interactive jQuery dev.</p>
  
  <p>However, in terms of a project file structure, i seem to be clueless and appear to be, perhaps, bloating things out of proportion.</p>
  
  <p>I've got a basic project boilerplate over on github: <a href="https://github.com/KingScooty/node-express-3.0-html5-boilerplate" rel="nofollow">https://github.com/KingScooty/node-express-3.0-html5-boilerplate</a> that works for me quite nicely.</p>
  
  <p>And now i'm looking to integrate <strong>Ember.js</strong>. However, i have no idea how to structure the directories. I'm thinking something along the lines of this:</p>
  
  <pre><code>project
  ├── app
  │   ├── collections
  │   ├── models
  │   └── views
  ├── node_modules
  ├── public
  │   ├── css
  │   ├── img
  │   └── js
  ├── routes
  └── server
      ├── environment
      └── logs
  </code></pre>
  
  <p>Socket io settings go in the server folder, along with all the node server config and environment config settings (development / staging / production). Static files and jQuery go in public, and the MVC app goodness goes in the app folder.</p>
  
  <p>But it doesn't feel right having a public folder separate from the app folder. Not to mention how i'd even go about including the various JS files in the MVC folder structure. </p>
  
  <p><em><strong>(Front end MVC development is something i know very little about, but this is what i'm trying to learn while also trying to integrate it into my Node environment)</em></strong></p>
  
  <p>If someone can point me on the right path for front end MVC development while utilising a node / socket io powered back end, that would be wicked!</p>
  
  <p>Cheers.</p>
  
  <p>-S</p>