Issue #441: Added persistent volume for evershop configuration in doc… #444
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.
docker-compose.yml
Important changes you have to make:
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Currently, the docker-compose.yml does not provide a persistent volume for the evershop application configuration, meaning that any configuration changes made would be lost when the container is restarted.
Issue Number: #441
What is the new behavior?
This PR introduces a persistent volume mapping in the docker-compose.yml file for the evershop application. This change allows users to retain their evershop configuration even after the container is restarted, enhancing data persistence.
Does this PR introduce a breaking change?