run-on-startup optional param for all jobs

[jtbry]

This pull request is in relation to Issue #79. I also have a use case for a data polling service that I would like to run once when the ofelia docker service starts up and then schedule from there. I stumbled across the issue and saw it open for help-wanted.

I added the RunOnStartup option to the BareJob struct to allow for it to apply to all job types.
Also added appropriate testing for RunOnStartup to the scheduler test suite
Also added documentation regarding the run-on-startup param to the jobs documentation

[ec-ecss]

@jtbry I've got a litte question with your PR
The execution via run-on-startup is actually blocking every other ofelia execution
As long as the command is not terminated, there is no other job registration
So I can't lauch, for exemple, a script that never ends (such a file listener in a specific folder)
My workaround is to create a intermediary script with "&" that call the effective script (the "&" is not correctly parsed in the ofelia command line attribute )
Do you think it's a bug or a feature ?

[jtbry]

@CaptainKant it is most likely a bug. The on startup jobs are started as parsed, in my testing I did not see a noticeable delay or anticipate a long blocking scenario. I’ll look at how other jobs are ran in a non blocking manner and see if it can be applied

[ec-ecss]

@CaptainKant it is most likely a bug. The on startup jobs are started as parsed, in my testing I did not see a noticeable delay or anticipate a long blocking scenario. I’ll look at how other jobs are ran in a non blocking manner and see if it can be applied

Ok. Just to let you know, I just noticed my workaround cause high cpu usage of the main docker-desktop process, for a strange reason.

[jtbry]

@CaptainKant it is most likely a bug. The on startup jobs are started as parsed, in my testing I did not see a noticeable delay or anticipate a long blocking scenario. I’ll look at how other jobs are ran in a non blocking manner and see if it can be applied

Ok. Just to let you know, I just noticed my workaround cause high cpu usage of the main docker-desktop process, for a strange reason.

This should be fixed in the most recent commit. The startup job now runs in a goroutine to prevent blocking. You should be able to use it normally now without your workaround.

[escoand]

When will this be released as a new docker image?

[jtbry]

When will this be released as a new docker image?

You can use this image including this functionality jtbry/ofelia:latest. I have published this image on my own from my fork while waiting for merge.

[ghostlexly]

I need this so bad 👍

[al-tr]

if you use docker compose, don't forget to add

...
  ofelia:
    depends_on: 
      - service-names
      - you-want-to
      - run-jobs-in
...

otherwise ofelia is very likely to start first and hit an unprepared container, and you'll have to manually restart it to rertigger the jobs