plugins/scheduler-docker-local/triggers.go

package schedulerdockerlocal

// TriggerSchedulerCronWrite force updates the cron file for all apps
func TriggerSchedulerCronWrite(scheduler string) error {
	return writeCronTab(scheduler)
}
refactor: move crontab writing code to scheduler-docker-local plugin The implementation was very heavily docker-local specific and thus didn't make a ton of sense to keep in the cron plugin. This also re-introduces changes from #5908 to parallelize the crontab generation (which is also specific to the docker-local scheduler) that were lost during a rebase. The impetus for this change was implementing a `cron:run` command. The logic for actually running the command isn't scheduler specific - merely invoking `dokku run` with the appropriate arguments - but all the logic around how the commands were retrieved were, so the change was made pre-emptively. 2023-07-02 02:43:55 -04:00			`package schedulerdockerlocal`

chore: rename trigger function 2025-06-10 23:36:10 -04:00			`// TriggerSchedulerCronWrite force updates the cron file for all apps`
			`func TriggerSchedulerCronWrite(scheduler string) error {`
refactor: rename cron entry to cron task This naming better suits what it is we are fetching. 2025-09-21 20:58:56 -04:00			`return writeCronTab(scheduler)`
refactor: move crontab writing code to scheduler-docker-local plugin The implementation was very heavily docker-local specific and thus didn't make a ton of sense to keep in the cron plugin. This also re-introduces changes from #5908 to parallelize the crontab generation (which is also specific to the docker-local scheduler) that were lost during a rebase. The impetus for this change was implementing a `cron:run` command. The logic for actually running the command isn't scheduler specific - merely invoking `dokku run` with the appropriate arguments - but all the logic around how the commands were retrieved were, so the change was made pre-emptively. 2023-07-02 02:43:55 -04:00			`}`