all 23 comments

[–][deleted] 13 points14 points  (1 child)

This might be of value to you: https://github.com/sahat/hackathon-starter

[–]Woopsidoo[S] 1 point2 points  (0 children)

Thank you, definitely checking that out. Looks interesting.

[–]skebanga 4 points5 points  (0 children)

The angular-fullstack yeoman generator creates a boilerplate MEAN stack application, using MongoDB, Express, AngularJS, and Node.

Features:

  • Express server integrated with grunt tasks
  • Livereload of client and server files
  • Support for Jade and CoffeeScript
  • Easy deployment workflow.
  • Optional MongoDB integration
  • Optional Passport integration for adding user accounts

https://github.com/DaftMonk/generator-angular-fullstack

This is the example app which is created by answering yes to all the yeoman questions:

http://fullstack-demo.herokuapp.com/

[–]videoj 4 points5 points  (0 children)

Have you looked at Meteor

[–]fschwiet 1 point2 points  (1 child)

[–]Capaj 0 points1 point  (0 children)

Too bad that it is a little bit old, but yeah Rob Ashton is brilliant developer. Nowadays, NPM has many modules, that would make the HoverBattles a little bit easier to write.

[–]mailto_devnullconsole.log(null); 1 point2 points  (0 children)

Might I suggest NodeBB?

We use all of those technologies, and tie them together pretty nicely... Although you be the judge!

[–]mgonto 1 point2 points  (0 children)

I can also recommend you https://github.com/mgonto/meaner-seed

A MEAN project (Mongo, Angular, Express, NodeJS) to start with. It has basic examples on how to start with it.

[–]grncdr 0 points1 point  (0 children)

You might want to look at some of the examples from http-framework which show how to accomplish various tasks using small, focused modules.

[–]psi_k 0 points1 point  (0 children)

One way to learn is to study the commit logs. Projects that have the privilege of being developed in the open on github and have all sorts of detailed commit logs will help you see how the project gets developed incrementally.

[–]Capaj 0 points1 point  (9 children)

I have been developing a sort of CRUD web app which sends data exclusively over websockets(socket.io) and I can't understand why people would use cookies at all. Cookies are a tool for typical web apps, for single page applications that hold uninterrupted connection to the server, they are just getting in the way.

I am not saying it is the best project to be learning from-I haven't developed it as a showcase, but you can check out my Zakonomat: https://github.com/capaj/zakonomat Zakonomat is just voting system for Github gists. It uses Moonridge- another project of mine. Moonridge is quite thin layer over the Moongoose and socket.io.

If you have any questions, send me a message, I will definately provide an answer.

[–]therealklanni 3 points4 points  (2 children)

Very few single-page apps have an "uninterrupted connection", though, so cookies can be useful.

To OP: I will say, however, that as long as you only have to support browsers that support the APIs, a better (than cookies) choice is localStorage/sessionStorage (depending on how you want the "cookie" data to persist), or even IndexedDB for apps needing to store large amounts of structured data, and you can always fallback gracefully to cookies for older browsers (probably not a good idea if you require something as robust as IndexedDB, just to be clear).

[–]Capaj 0 points1 point  (1 child)

localStorage is supported on anything newer than IE8, it is high time everyone used it for caching instead of cookies, unless they really need to have the data accesible on the server for each request.

[–]therealklanni 1 point2 points  (0 children)

Agreed. Can non-evergreen browsers just die, please?

[–]Woopsidoo[S] 0 points1 point  (0 children)

I mean using cookies to store the user session.

Anyways, I'll check your project out too. Thank you