Creates a symbolic link to take live changes for SWAGGER_JSON file in Docker #4024
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.
Description
When we add
SWAGGER_JSONfile to Docker container, it simply copies the JSON file into/usr/share/nginx/html. So the JSON shows proper content for the first.If we make changes to the local JSON file while the Docker container is running, it will not take the live changes. We will need to restart the container in order to see the changes again.
Creating a symbolic link instead of copying the file can be a better option to solve this issue.
Motivation and Context
How Has This Been Tested?
docker build .command created the new docker image successfully, after this change.Screenshots (if appropriate):
Types of changes
package.json)Checklist: