msavin
commented
6 years ago I think this might answer your question:
1- Jobs Debugging UI for development purposes only. I will have a
production option soon.
2- Jobs.collection() gives you direct access to the Jobs collection,
which you can use in any Meteor publication
On Fri, Jul 27, 2018 at 2:17 PM, tosinek notifications@github.com wrote:
Hi, I may have a use case for direct DB access.
When a user logs in, the code starts periodic data refresh and the data is synced with Mongo. Each user queries their own data from SQL. I would like to display in GUI e.g. when the next update is due. There is quite complex logic on what data and when to sync (there is several layers of updates) and I don't have a good solution for it (I guess I would have to start querying the server periodically using methods). Instead, I would like to subscribe to all user's scheduled jobs and that way, I would always know what has been scheduled.
(my current "solution" is that the client contains code with Meteor.setInterval that triggers some of the jobs without scheduling them upfront. This gets too messy, as there are situation, when the server can actually schedule something on users' behalf (data driven) but there is no easy way how to tell the client)
The "jobs_data" collection seems to be scoped to a file, and Meteor won't let me create another collection/subscription (on the client). Could you expose the collection variable in a way I would be able to create a publication for it? Or is there a workaround that would not require your help? (the Jobs.collection is available only on server and I can't create minimongo collection on the client)
Also, with the UI widget, where is its code? I could only find a minified file in my Meteor packages (which is hard to read). How does it handle user permissions? Or can everyone open the job schedule and start messing up with jobs? I would like to be able to edit the table and add e.g. "who triggered this job" column, as my arguments are currently an object, not individual strings.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/msavin/SteveJobs..meteor.jobs.scheduler.queue.background.tasks/issues/60, or mute the thread https://github.com/notifications/unsubscribe-auth/AB7-g7zNco6Q27Kvau1G7HawiscbL729ks5uKwT2gaJpZM4VjZ0L .
tosinek
ZhaopingLuo
charlesdeb
joephuz
Hi, I may have a use case for direct DB access.
When a user logs in, the code starts periodic data refresh and the data is synced with Mongo. Each user queries their own data from SQL. I would like to display in GUI e.g. when the next update is due. There is quite complex logic on what data and when to sync (there is several layers of updates) and I don't have a good solution for it (I guess I would have to start querying the server periodically using methods). Instead, I would like to subscribe to all user's scheduled jobs and that way, I would always know what has been scheduled.
(my current "solution" is that the client contains code with Meteor.setInterval that triggers some of the jobs without scheduling them upfront. This gets too messy, as there are situation, when the server can actually schedule something on users' behalf (data driven) but there is no easy way how to tell the client)
The "jobs_data" collection seems to be scoped to a file, and Meteor won't let me create another collection/subscription (on the client). Could you expose the collection variable in a way I would be able to create a publication for it? Or is there a workaround that would not require your help? (the Jobs.collection is available only on server and I can't create minimongo collection on the client)
Also, with the UI widget, where is its code? I could only find a minified file in my Meteor packages (which is hard to read). How does it handle user permissions? Or can everyone open the job schedule and start messing up with jobs? I would like to be able to edit the table and add e.g. "who triggered this job" column, as my arguments are currently an object, not individual strings.