Improvements Wishlist
Reorganize data directory do make clear what paths are context/configuration and what are downloaded/built
my /data directory has more than 17GB with 4 screens.
I like to have backup of important data, and that is too much for only 4 screens
There are some folders that clearly can be removed from backup (idf, esphome,build), but the *.json *.key *.lock appear to be context of app and are good candidates for backup.
can this be reorganized to separate the downloaded/build paths in a single space like /build_data/ and leave the tessera internal files separate like the /config path ?
Discussion 1
Add a commentI have already changed my docker-compose to separate the idf/build/esphome but making a single volume to mount for any temporary files are better than having 3 or more.