Multiple (separate/namespaced) Meteor client codebases per single Meteor app

Question

I'm working on rewriting an existing application with Meteor that has two fairly distinct use cases (an administrator account and user account). Both could be considered separate apps in terms of functionality, but share the same back end database.

Is there any way to "namespace" or otherwise define separate clients so that Meteor only packages and sends assets for the client that's being accessed. For ie. the meteor-router could push different clients for the /admin* space and the /user* space, that way there's no unnecessary overhead downloaded for either client.

I expect this is outside the scope of what's within the means of a Meteor smart package like meteor-router.

Answer 1

You can always create two applications that connect to the same database. Shared server code may be put in a package and included in both, so there will be no need to repeat it.