Multiple instances & micro services

[akiarostami]

Hi,

First of all, thank you for the wonderful job!

My meteor app has two parts, both standard Meteor apps, using the same Mongo database.

Admin app: I run this app on my local (development) machine using the default settings (port 3000, meteor-handled mongo). I have no problem running this using Meteor-helper.

User app: I run this app on a different port (5555) and connect it to the admin app's mongo instance, using the following settings in mup.json file:

{
  "env": {
    "PORT": 5555,
    "MONGO_URL": "mongodb://localhost:3001/meteor"
  }
}

When I try to run the User app, I get a bunch of errors, including "No scheme found in URI undefined".
When this happens, I also get "Unexpected mongo exit code 0. Restarting." on the Admin app.

I know this may look a bit complicated, but it's actually very easy to replicate. It would be great if you could take a look at this problem.

Thank you!

[coopermaruyama]

Are you trying to run these both off of Atom at once? Or is it one atom and another just the regular way from a terminal?

[akiarostami]

I have two separate projects opened in two different atom windows. I have no issues running it from a terminal, but can't run it from Atom.

[PEM--]

I'm lagging behind here too. Didn't see the notifications.

This package was designed to launch a single instance of Meteor... But with the rise of micro-services, this case starts to be a mandatory feature.

Currently, the analyzed workspace is the first being launched. The settings overrides the environment variables when Meteor is launched letting it knows about the content of the mup.json. What should be done here, is to parse the content of the mup.json file each time a Meteor process is launched and link the read environment variables to the executed process. I guess that the current Atom's workspace could be extended to set the process on it.

That would to the trick for the moment but that would not tackle the problem of micro-services. I will think about it.

PS: @akiarostami, I got the same issues as yours on OrionJS's CMS. I would like to separate the admin app from the main public app. For the moment, I haven't investigate too much in this topic but surely will.

[PEM--]

@akiarostami I've modified the title of the issue to bring more meaning 😉

[akiarostami]

Thank you! 👍