This is related to a previous question I asked about conditionally sending document data to the client in meteor.
Lets say I have a parse-like data editor/browser available for user accounts marked as system admin, as well as some pages that show logging information about the app. I’m using meteor-router and a filter to accomplish this.
99% of users won’t need to to see those interfaces, but the (massive amounts of) javascript for them is still sent to the client. The admin specific javascript and templates are separated into their own files, how can I make sure they are not sent to the client unnecessarily (when the logged in user is not an admin)?
Is the best option really to split the admin interface into a separate app and point it at the original’s mongo?
If you don’t want Meteor to load your client-side scripts automatically, you could place them in the /public directory and load them yourself when you need them.
However, in the case of an admin environment, it may actually be better from a software development perspective to separate all of that into its own app, pointing to the same database like you said.