Replies: 0 comments 3 replies
-
I've added a var we can leverage for this, its a larger body of work that'll come over time |
Beta Was this translation helpful? Give feedback.
-
this becoming more important the further we delve into this, migration path for tooling might become a real issue with anything we want to do now. |
Beta Was this translation helpful? Give feedback.
-
We are going to either have to use symlinks for tools that don't support passing a config option or something else and write standards for adding new items to RetroNAS for this to be feasible. I'm going to park this for now because its a larger body of work than anticipated and wont be done until other things are done. Going to convert this to a discussions for now so we can consider what we do here with new tools, can convert back when ready to do the work |
Beta Was this translation helpful? Give feedback.
-
We need to create a configuration directory outside of the main config dir so that users settings can persist over re-installations
e.g.
/home/{{ retronas_user }}/.retronas/
This will need to be also handled as part of the username change feature
Beta Was this translation helpful? Give feedback.
All reactions