Details
-
Story
-
Status: Complete
-
Highest
-
Resolution: Done
-
None
-
None
-
None
-
13, 14, INDY 17.21, INDY 17.22, INDY 17.23
Description
We need to use proper file folder paths for system service: usr, var, etc, user-configuration vs system configuration, folders for network configuration so multiple networks can co-exist
The most urgent task here is likely the file and folder location refactor, we will want to reorganize how things are laid out as soon as we can, before we pick up more production use cases and grow the network. I walked through this with Dan and Devin and have attached an outline of what we discussed (see attached image). Notice the paths under /var, /etc and $HOME/.indy. The variables at the top of the board could be used as potential substitutes. We also talked about having some sort of environment variable(s) so that system users can overwrite the home folder location to something more suitable. Notice that this was from a brainstorming session, there is nothing set in stone. Please add your thoughts and suggestions. Obviously some plan as to how we can migrate files from existing locations in the current network will be important. I look forward to hearing what tickets you think will be needed.
Attachments
Issue Links
- blocks
-
INDY-838 Incubation: Check that Indy Node, CLI and SDK can be used on one PC
-
- Complete
-
-
INDY-912 Fix documentation: init_indy_node now must be called several time for each desired network
-
- Complete
-
- relates to
-
INDY-925 Implement client migration for rebranding and multiple pool networks support upgrade
-
- Complete
-