Per resource scheduling #222
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Nov 5, 2018
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a longstanding branch, mainly implementing #132 but also introduces architectural changes: the split (optional) into a GHC web-process (web-Flask-UI) and a pure GHC Runner daemon process. This was needed as any random run-frequency cannot be maintained via
cron.Most of this work was performed on the OSGeo Code Sprint in March 2018, Bonn. It builds on ideas from #175, mainly the introduction of
APScheduler.Many other changes went in as well to make running a Resource in a multi-process environment as would happen when running with
gunicornoruwsgi.