Merging the UI and History (3rd party extensions) into main db-scheduler #665
Unanswered
adamalexandru4
asked this question in
Q&A
Replies: 2 comments
-
It makes sense, and if I had more time I think it would make the package better, but they were created as separate projects to avoid increasing the maintenance work required for db-scheduler |
Beta Was this translation helpful? Give feedback.
0 replies
-
I understand the concerns about maintenance, but features like history (logs), UI are definitely valuable for a DB scheduler — similar to what JobRunr offers. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
What do you think about integrating these third-party extensions into the main product?
This way, they’ll stay in sync and align with db-scheduler’s release cycle.
bekk/db-scheduler-ui
rocketbase-io/db-scheduler-log
Beta Was this translation helpful? Give feedback.
All reactions