Make configuration more flexible to simplify deployment in other containerized execution environments #208
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
…ntainerized execution environments (e.g. k8s), since combination of application configuration and Dockerfile only allowed deployment in docker-compose environments using the existing compose files - Upgrade npm to newer version to get rid of warnings during the Docker build process
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.
Hi,
I provided small optimizations to make it easier using the application in other containerized execution environments (e.g. k8s), since given combination of application configuration and Dockerfile only allowed deployment in docker-compose environment using the existing compose files.
I also upgraded npm in the Dockerfile to a newer version to get rid of warnings during Docker build process.
Best regards,
Andreas