When running the "parties" example locally, if I first specify my MONGO_URL to use an already existing instance of mongo meteor mongo , which reports that the meteorite does not work, although it is, and although it connects just fine to a separate instance of mongo.
If you run the meteor application without specifying a separate MONGO_URL, no problems meteor mongo works as expected
Now I also tried setting MONGO_URL before running meteor mongo no avail. I have not tried deploying the application to find out what will happen.
Another troubleshooting attempt - after starting the application, I try to connect using meteor mongo with the flag --url localhost:27017 , which asks for Password:. This should give me the url to connect to the database instance, and the password request is also not mongo, as
a) I do not have authentication in my local instance
b) Even if the local instance is not running and you run meteor mongo , it still asks for a password.
In meteor documentation, this is noted under meteor mongo:
You should now have an application running locally with meteorite runs. It will be easier> in the future.
Is that what they mean?
Obviously, it has nothing to do with the fact that I have access to the shell from the meteor object to my local instance, since I can always access the shell just by typing mongo, but my deployment problem is, and I have to get access to the shell, then, this can be a problem.