Prod fixes #30
Merged
Prod fixes #30
+52
−1
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
added 6 commits
January 14, 2026 15:57
cokernel
approved these changes
Jan 16, 2026
Member
cokernel
left a comment
cokernel
left a comment
There was a problem hiding this comment.
I am happy with this.
I made minor suggestions regarding variable propagation and I am happy with the modifications made in response.
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.
Adds @cokernel's cache regeneration scripts to the container with some modifications to allow a more host agnostic deployment.
Regenerating the cache requires environment variable SOLR_URL which is included in the generated .env.prod file in ukl-ansible-playbooks. I am leaving this feature out of ci and dev because the mounted XML cache would need to have a matching entry in solr and it would add unnecessary traffic to the solr server.
The script targets the docker compose service named "web" wherever it is ran, so it'll only regenerate its own cache (e.g., an euk_blue-findingaid-1 container would only regenerate the cache for the blue service).