Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

what to do with ./data/ ./config/ ./services/ #2

Closed
marc-portier opened this issue May 15, 2024 · 1 comment
Closed

what to do with ./data/ ./config/ ./services/ #2

marc-portier opened this issue May 15, 2024 · 1 comment
Assignees

Comments

@marc-portier
Copy link
Contributor

running docker-compose up introduces automatically these folders, owned by root

probably a very logical side-effect, but is now rather unexpected, so should get documented (see #1 ) as well as possibly be added to .gitignore to avoid these ever getting part of the repo?

@cedricdcc
Copy link
Collaborator

In vocabserver app the ./data folder holds all the temp data that can be reused if the containers crash so this can be put into the .gitignore file.

But the ./config folder was essential for the other containers to work. This info should have been placed in the containers themselves for deployment for the whole system to work.

Same with the contents of the ./services . The dockerfile should have taken care of this so it is not necessary to further pursue this issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants