Add XLoader image to run in it's own container, separate from the CKAN UI container #76
Conversation
This file contains hidden or 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
Dockerfile, Makefile and setup process
kowh-ai
changed the title
|
This shouldn't be difficult to implement in xloader, I've put down the work needed here: |
|
It seems suboptimal for the CKAN site URL to be |
not needed, was used for debugging
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.
Fixes #66
This PR creates an XLoader image to be used as a replacement for DataPusher.
This XLoader PR was merged recently: Feature/custom xloader site url rebased which implemented a new config option
ckanext.xloader.site_urlthat allowed XLoader to communicate back to the CKAN UI container running in a Docker network