Closed joncursi closed 7 years ago
I'm not sure if it makes a difference, but I am using a dedicated MongoDB replica set, not the Mongo instance built into Meteor.
Derp! That was it! Since I'm not using the built-in Mongo on the application server, I don't need to DDP connect to it. I can just instantiate a new JobCollection
:
const jc = JobCollection('jobs', {
noCollectionSuffix: true,
});
console.log('here');
const test = jc.getJob('xJsCEBXFBMEeMP9Nj');
console.log(test);
I am having the same issue mentioned here but I can't seem to figure out what I am missing.
I have to Meteor servers, one is my application server and the other is a jobs server that needs to do the work.
On the application server (running locally on port 3000):
I can see new jobs being stuffed into the
jobs
collection in MongoDB. Great!Now, on the jobs server (running locally on port 6000):
I see that
"here!"
gets logged out to console, but Meteor never prints the job I asked for because it gets hung up onjc.getJob(...)
.What am I doing wrong here? 😿