first thoughts on pa_job_engine - to keep overall pa_job engine state, also a pa_job_state in each action also a wait_for so we can do basic handling of jobs and dependencies
This commit is contained in:
2
TODO
2
TODO
@@ -20,6 +20,7 @@
|
||||
to keep html easy, can keep routes:
|
||||
/jobs/import/ -> importlog.html
|
||||
/jobs/ai/ -> importlog.html???
|
||||
/jobs/move/ -> importlog.html???
|
||||
|
||||
but not sure if any job won't have passes, num files, etc. BUT if it ever does this is how we deal with it
|
||||
|
||||
@@ -32,7 +33,6 @@
|
||||
-> when job finished, then Import Files (import_dir only)
|
||||
-> when job finished, the set state: awating jobs
|
||||
|
||||
|
||||
implications, pa_job needs to know if it depends on another, e.g. do find before import (in example above)
|
||||
pa web needs to show status for the job engine IN YOUR FACE when not at awaiting jobs yet, afterwards, maybe a simple jobs(<badge>) that is clickable on the gui?
|
||||
|
||||
|
||||
Reference in New Issue
Block a user