Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Scheduled actions in app backend in favor of crontabs #24

Open
vipul-sharma20 opened this issue Aug 12, 2021 · 3 comments
Open

Scheduled actions in app backend in favor of crontabs #24

vipul-sharma20 opened this issue Aug 12, 2021 · 3 comments
Assignees
Labels
enhancement New feature or request

Comments

@vipul-sharma20
Copy link
Owner

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.

@vipul-sharma20 vipul-sharma20 added the enhancement New feature or request label Aug 12, 2021
@vipul-sharma20 vipul-sharma20 self-assigned this Aug 12, 2021
@avvijeet
Copy link

So basically add a scheduler in app backend?

@avvijeet
Copy link

And the app itself would be a scheduler-server?

@vipul-sharma20
Copy link
Owner Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants