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

Feature: Use Hangfire to handle and manage background and scheduled jobs #1079

Closed
3 tasks
hocinehacherouf opened this issue Aug 11, 2022 · 1 comment · Fixed by #1135
Closed
3 tasks

Feature: Use Hangfire to handle and manage background and scheduled jobs #1079

hocinehacherouf opened this issue Aug 11, 2022 · 1 comment · Fixed by #1135
Labels
enhancement New feature or request
Milestone

Comments

@hocinehacherouf
Copy link
Contributor

Describe the solution you'd like

Use Hangfire to handle and manage background and scheduled jobs

Example: Hangfire can be use to trigger jobs to sync IoT Hub Portal database and Azure IoT Hub

Remarks:

Jobs can be triggered as:

  • Background jobs
  • Scheduled/Cron
  • Manually using Hangfire Dashboard or custom screen/api to interact with Hangfire

Features to enable:

  • To avoid data loss on the traceability of jobs; Use database to persist jobs infos and metadata related to Hangfire
  • Enable Hangfire Dashboard (or create custom pages on IoT Hub Portal) to monitor and administer jobs
    • Secure access to Hangfire Dashboard: Only for Admins
@kbeaugrand
Copy link
Member

Hangfire is under LGPL License.

Would be preferable to use MIT licensed Framework to operate...

@kbeaugrand kbeaugrand linked a pull request Aug 28, 2022 that will close this issue
9 tasks
@kbeaugrand kbeaugrand added this to the S38 milestone Aug 29, 2022
@kbeaugrand kbeaugrand moved this to :rocket: Ready in IoT Hub Portal Aug 29, 2022
This was referenced Aug 29, 2022
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
Status: 🚀 Ready
Development

Successfully merging a pull request may close this issue.

2 participants