Just wondering what is the project structure and architecture of large Meteor projects. I’m quite interested to see what big Meteor applications like
lemlist @acemtp and Qualia @veered use. I’m sorry if is should not have tag you. Do you use MVC, MVVM or any other patterns. All replies are welcome.
Thanks in advance
I always really liked the suggested structure on the (now gone) Meteor Tuts website.
The content is still on GH, so you can build and view it locally: GitHub - cult-of-coders/meteor-tuts: Meteor Tutorials - From Noob to PRO
Specifically the page on structure here:
This file has been truncated.
title: 'Overall Structure'
description: Let's bring it to a degree of order
disqusPage: 'Chapter 3: Structure'
So, we discussed about many concepts and we described where to put them. But the thing is,
it doesn't really matter that much, what we describe here are a set of practices, there's no such thing
as the best way, or the way. Whatever you choose, be consistent and try to document it.
To give you an overall image, it will look something like this:
# This is where you import everything you need on server to start
# Most likely it will be just: import '/imports/api/server'