Open scusi opened 6 years ago
For now the answer is: Copy your configuration and addressbook yaml files from machine A onto machine B.
On a unix machine you could use tar to create an archive file with config and addressbook.
tar -cvzf ssconf.tar.gz $HOME/.config/secureshare/client/$ssUsername/*
Then you have to bring that file (ssconf.tar.gz) onto machine B and put it into the same path.
$HOME
is your local user directory, e.g. /home/tom
or on windows C:\Users\tom
$ssUsername
is your secureShareUsername, use secureShare -show-user
to get it.
In the long term it would be nice to have some possibility to use secureShare to just copy the config from one machine onto another.
Once Issue https://github.com/scusi/secureShare/issues/3 and https://github.com/scusi/secureShare/issues/5 will be implemented this should be fairly easy.
A clone-config option would be nice. So you could - on machine B - do like this:
secureShare -clone-config <secureShareUsername>
It would ask for your minilock Email and Password, create the keypair, go to the server and downloads your config and addressbook and save it locally on machine B.
@scusi, it seems the project has been abandoned, or not?
@scusi, it seems the project has been abandoned, or not?
Not really abandoned, i just have not done anything on it lately, too busy with other stuff. The example/default server is also not running anymore. If you are interested and want to play with it, i can bring the server back, no problem.
After i installed secureShare (client only) on machine A and registered for an account. How can i use the same account on machine B?