Standardised folder structure - AEGEE/oms-profiles-module GitHub Wiki

Without losing too much time into discussion, I summarise the findings for Node.js good practices and conventions for file structure

As per here, there is no standard, thus I set our standard to be:

README, licences, and other files
package.json      <!-- handle our npm packages -->
tests/            <!-- container of all test data -->
lib/              <!-- container of all application data -->
-- server.js         <!-- setup our application -->
-- app/
------ models       <!-- our models if we'll ever have them -->
---------- user.js  <!-- e.g. user model -->
------ routes.js    <!-- all the routes for our application -->
-- config/
------ auth.js      <!-- will hold all our client secret keys (facebook, twitter, google) -->
------ passport.js  <!-- configuring the strategies for passport -->
-- views/
------ index.hbs    <!-- show our home page with login links -->
------ login.hbs    <!-- show our login form -->
------ (...and so on)
-- public/          <!-- container for our static files like css-->
------ style.css
------ (...and so on)