Consolidate user-configurable files into data directory
#66
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.
Summary
This PR reorganizes the project structure by moving all user-modifiable files and directories into a single root-level folder named
data.The following items have been relocated:
optimization_policies/data/policies/example_rules/data/examples/rules/edgemining.dbdata/db/edgemining.dbThe following items have been added:
data/db/backups/Motivation
The primary goal is to simplify persistent storage management, especially for Docker deployments. By grouping all operational data in one place, users only need to mount a single volume (e.g.,
/host/path:/app/data) to persist their database and configurations, rather than managing multiple individual mounts.Changes
datadirectory.data.Dockerfileandcompose.yamlto reflect the new structure.READMEto guide users on how to access these files.Impact
IMPORTANT: This is a breaking change for existing installations. Users must move their existing
edgemining.dbandpolicy folderinto the newdata/directory to maintain their data.