Open vipul-sharma20 opened 3 years ago
So basically add a scheduler in app backend?
And the app itself would be a scheduler-server?
Idea is to basically remove the manual step of setting up scheduled actions (crons here) to generate events / messages on Slack for standups.
Currently, scheduled actions are reminders to individuals (there can be more than 1 reminder based on team's preference) and publishing the final standup submissions. These need to be setup as crons which is a separate setup.
I had worked on reducing the steps involved in setting up the standup backend itself + configuring it. The configuration step is just running a slack slash command and configuring your settings in a dialog box. In best case scenario you would like to be get going after this step and hence I would want to remove this cron and maybe handle by the backend layer itself.
So yes, a scheduler in the application backend or if there are any other better ways to do it. Not thought about it.
Is your feature request related to a problem? Please describe. Deployment has to maintain crontabs for notification/publishing in a different place than main application.
Describe the solution you'd like App backend should be able to handle all the scheduled actions instead of maintaining crons.