You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the solution you'd like
Right now, by default and without the possibility of modification, all data is saved in /DATA. I would like it to be possible to somehow establish the path in which the data should be stored. Being able to even separate the data referring to configurations and "work" files of the different containers, from the user files.
I don't know the complete structure of casaos, but one option would be to define the variable in the main configuration file and then have it read by the application management module to use it to generate the containers.
Additional context
It can be done in a similar way to how they do it in ansible-nas:
Here they define the route for all container data:
Describe the solution you'd like
Right now, by default and without the possibility of modification, all data is saved in /DATA. I would like it to be possible to somehow establish the path in which the data should be stored. Being able to even separate the data referring to configurations and "work" files of the different containers, from the user files.
I don't know the complete structure of casaos, but one option would be to define the variable in the main configuration file and then have it read by the application management module to use it to generate the containers.
Additional context
It can be done in a similar way to how they do it in ansible-nas:
Here they define the route for all container data:
https://github.com/davestephens/ansible-nas/blob/2151f6287b6394c1729f55e7e22b86378da7e818/roles/ansible-nas-docker/defaults/main.yml
And here for the user data:
https://github.com/davestephens/ansible-nas/blob/2151f6287b6394c1729f55e7e22b86378da7e818/group_vars/all.yml
The text was updated successfully, but these errors were encountered: