Add ./data directory for volume mounting in docker-compose.yml
This change modifies docker-compose.yml to use bind mounts with the ./data directory for easier data management/backups.
I don't think this should be default. There is no need to backup all cache and static app data. Also you should not backup the database files directly (especially when the container is still running) but do a database dump and archive that.
Agree that not all data should be kept in the same directory, but to me it's helpful to have the database in the same directory. It took some time to figure out which volume contains what kind of data and where they are located.
Immich has database in the same directory as default, and recently it added automatic database backup.
Dawarich's documentation says the instruction on database backup was inspired by immich, so I feel it's not that bad idea to put data in the same directory, with an eye toward automatic backup option in the future.
I don't think this should be default. There is no need to backup all cache and static app data. Also you should not backup the database files directly (especially when the container is still running) but do a database dump and archive that.
An example of volume mounting is already present in https://github.com/Freika/dawarich/blob/master/docker/docker-compose_mounted_volumes.yml and is not supposed to be the default option, at least as of now.
Thank you for your PR though!