Open aschaeffer opened 6 years ago
Doesn't this actually belong into a user plugin? I mean besides the autosave usecase none is really critical for our future development. And why not just autosave after changes are made?
examples! :-)
This feature isn't meant for developers but server administrators and end users. Server admins and end users simply doesn't have to do these tasks manually any more. It also helps to reduce the support questions, because content and user interfaces are kept up to date without any action required by the server admin or end user. Also plugin developers can use the scheduler for their needs.
Enhance Inexor Flex with a scheduler to trigger time-based events.
Examples for time-based events
updateMediaRepositories
updateInterfaces
updateReleaseList
updateServerList
restartServerInstance
autoSaveMap
You got the idea.
Inexor Tree
Tasks
/tasks/scheduled/{taskName}
/description
/cronPattern
/action
/service
/method
/parameters
0
= parameterValue1
= parameterValueupdateScheduler()
executeAction(taskNode)
service
from the applicationContext and executes themethod
using the given parametersloadConfig(filename = 'scheduler.toml')
saveConfig(filename = 'scheduler.toml')
See also