Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I have a similar situation to you but ended up solving it in a completely different way. It is now available as a Meteor smart package:</p> <blockquote> <p><a href="https://github.com/mizzao/meteor-partitioner" rel="nofollow">https://github.com/mizzao/meteor-partitioner</a></p> </blockquote> <p>The problem we share is that we wanted to write a meteor app as if only one client (or group of clients, in my case) exists, but that it needs to handle multiple sets of clients without them knowing about each other. I am doing the following:</p> <ul> <li>Assume the Meteor app is programmed for just a single instance</li> <li>Using a smart package, hook the collections on server (and possibly client) so that all operations are 'scoped' only to the instance of the user that is calling them. One way to do this is to automatically attach an 'instance' or 'group' field to each document that is being added.</li> </ul> <p>Doing this correctly requires a lot of knowledge about the internals of Meteor, which I've been learning. However, this approach is a lot cleaner and less resource-intensive than trying to deploy multiple meteor apps at once. It means that you can still code the app as if only one client exists, instead of explicitly doing so for multiple clients. Additionally, it allows you to share resources between the instances that can be shared (i.e. static assets, shared state, etc.) </p> <p>For more details and discussions, see:</p> <ul> <li><a href="https://groups.google.com/forum/#!topic/meteor-talk/8u2LVk8si_s" rel="nofollow">https://groups.google.com/forum/#!topic/meteor-talk/8u2LVk8si_s</a></li> <li><a href="https://github.com/matb33/meteor-collection-hooks" rel="nofollow">https://github.com/matb33/meteor-collection-hooks</a> (the collection-hooks package; read issues for additional discussions)</li> </ul>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload