Currently, vsw client uses default locations for its wallets, config files etc.
The default is ~/
We need a way to set this to a different directory that the user can choose.
This is needed to allow the user to copy wallets to another machine or survive a container.
The test scenario I am looking is:
run a container, install vsw, use vsw normally
quit the container
restart a new container, continue to use previous created wallets and DIDs etc. etc.
In a laptop, I can map a local disk based directory to the container that will keep those files persisted. But I don't know how to do that to /home.
In a public cloud, same may be easier if it is not /home.
This will allow me to test functions with pre-existing wallets. So far, all tests use brand new wallets.
tar 3 directories: .indy_agent, vsw_logs, vsw_tools, save somewhere persistent.
and copy that back when a new container starts
that seems to work ok. Closing this for now.
Currently, vsw client uses default locations for its wallets, config files etc. The default is ~/ We need a way to set this to a different directory that the user can choose. This is needed to allow the user to copy wallets to another machine or survive a container. The test scenario I am looking is:
In a laptop, I can map a local disk based directory to the container that will keep those files persisted. But I don't know how to do that to /home. In a public cloud, same may be easier if it is not /home.
This will allow me to test functions with pre-existing wallets. So far, all tests use brand new wallets.