meteor-platform coffeescript fourseven:scss aldeed:collection2 matb33:collection-hooks accounts-password accounts-facebook momentjs:moment reywood:publish-composite dburles:collection-helpers reactive-var reactive-dict zimme:active-route alanning:roles dburles:factory digilord:faker msavin:mongol service-configuration arillo:flow-router-helpers kadira:flow-router kadira:blaze-layout useraccounts:flow-routing useraccounts:bootstrap mplatts:accounts-ui-bootstrap-4 meteorhacks:npm npm-container mplatts:event-emitter2
- Flow router installed
- Bootstrap 4 manually installed (remove client/lib/bootstrap if you don't want it)
- custom accounts UI works with Bootstrap 4
- eventEmitter2 installed on server - called E (E.emit('event', val))
- User schema setup
- Example file structure for collections
- Facebook sign up captures name, email and profile picture URL
- loading bar when websockets is active (like Youtube load bar up the top of the screen)
formattedDatehelper for date formatting
- loading bar like Youtube's is shown up top when DDP on the go
Clone and rename
git clone email@example.com:webtempest/meteor-boilerplate.git projectname cd projectname
Adding Facebook sign in
Get your app ID and secret and put it in your
settings-example.json). If you look in
server/setup/facebook.coffee I create the Facebook service provider and make it so name, email and profile picture is stored in the user's profile (if they sign up via Facebook).
Remove helper files
There are files dotted around in certain folders to help you get started. Mostly you can just keep them there and use them as a reference. Though you'll probably want to change
Folder/file naming and patterns used are opinionated and open for debate. Please create issues or PR's for suggested new patterns.
Templates are named like this:
Why not use packages?
Telescope (a large and successful open source Meteor app) doesn't actually have any application code. Rather the creators have split the project into packages.
Packages offer better modularity and the ability to specify dependencies. In larger projects I would seriously consider using this pattern.