You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a follow up of other PRs like #418 & #431
Since the dasboard is another app we can't listen to the events directly on the dashboard..
Also, as we're only serving/using static pages (not another node.js server) we don't have APIs or routes on the dashboard (so we can't call any API back either)
Implementing a more advanced messaging mechanism (queues, web sockets) is pretty much impossible task atm, unless we convert the dashboard to a fully node.js app (But currently the dashboard does not even build using other option than "output:export" on nextConfig, so that is another limitation.. and we probably don't need another full node.js app anyway
What we can do atm is have some sort of pooling mechanism to get the status of the latest admin commands...
When we issue the admin commands, we get a "job id" as part of the 200 response, so we can ask about his execution a few seconds later.. (right now we just send a random msg saying the command was delivered without follow up)
When we catch/listen the events, we update the job status on the list of "pending execution"
Once the job is cleared/finished and dashboard has received that info at least once, the job is cleared permanently from the list
The text was updated successfully, but these errors were encountered:
This is a follow up of other PRs like #418 & #431
Since the dasboard is another app we can't listen to the events directly on the dashboard..
Also, as we're only serving/using static pages (not another node.js server) we don't have APIs or routes on the dashboard (so we can't call any API back either)
Implementing a more advanced messaging mechanism (queues, web sockets) is pretty much impossible task atm, unless we convert the dashboard to a fully node.js app (But currently the dashboard does not even build using other option than "output:export" on nextConfig, so that is another limitation.. and we probably don't need another full node.js app anyway
What we can do atm is have some sort of pooling mechanism to get the status of the latest admin commands...
When we issue the admin commands, we get a "job id" as part of the 200 response, so we can ask about his execution a few seconds later.. (right now we just send a random msg saying the command was delivered without follow up)
When we catch/listen the events, we update the job status on the list of "pending execution"
Once the job is cleared/finished and dashboard has received that info at least once, the job is cleared permanently from the list
The text was updated successfully, but these errors were encountered: