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.
Motivation and context
use .env for docker compose environment #7311
When I use CVAT with Docker Compose, I find it necessary to remember which version of CVAT I am using. However, I suggest maintaining CVAT versions and any customizations in a .env file, as it could reduce the number of properties that need to be remembered.
In the current commit, only CVAT VERSION and HOST are included, but I think it might be beneficial to gradually expand this functionality.
Please let me know your thoughts.
Thank you.
How has this been tested?
Checklist
develop
branchuse .env for docker compose environment #7311
(cvat-canvas,
cvat-core,
cvat-data and
cvat-ui)
License
Feel free to contact the maintainers if that's a concern.