Store generate config locally for repeatable builds #103
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
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 PR makes the following changes to how dockerfiles are templated:
yqpython dependency for json parsing3.12.2By storing the shortname data locally, it can be referenced more easily by the templates instead of translating env vars.
My goal with this PR is to centralize the template config in the json files, to make it easier to add additional config data for the docker-compose files. Eventually, it would be nice to completely configure it based on data in server cfg files (like here)
After this PR, I plan on fetching distro and server info to use in the dockerfile.
No changes to generated files