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

Review usage of configuration folders #497

Open
amedranogil opened this issue Jul 24, 2018 · 0 comments
Open

Review usage of configuration folders #497

amedranogil opened this issue Jul 24, 2018 · 0 comments

Comments

@amedranogil
Copy link
Member

configuration folders should be considered read only; or at least they may be set to read only. This means that some modules when writing to configuration should check if they have permission and if not use the data folder, which should have read and write permissions always. Of course this implies they should also look for configuration in data folder.

Example: mw.managers.space writes peer.ids to config folder, but if this folder has no writing permissions this operation fails.

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

No branches or pull requests

1 participant