Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migration from KeySAVe (Electron) #181

Open
Cu3PO42 opened this issue Jan 22, 2018 · 5 comments
Open

Migration from KeySAVe (Electron) #181

Cu3PO42 opened this issue Jan 22, 2018 · 5 comments

Comments

@Cu3PO42
Copy link
Owner

Cu3PO42 commented Jan 22, 2018

When migrating from KeySAVe the Electron app to the web application, keys and formatting options should be transferred.

There are multiple ways of going about this

  1. Tell the user where his configuration files are and have them upload them explicitly
  2. Push an update to KeySAVe (Electron) that has a 'migrate to web version' button that will automatically transfer all required data
  3. Release a separate migration helper utility that will work similar to option 2

Please comment on which option you would prefer and why. If you can think of other technically feasible solutions feel free to mention them as well.

@robdy
Copy link

robdy commented Jan 23, 2018

I'd go for option 2 as it's most friendly. How the keys will be stored by the way? External database?

@Cu3PO42
Copy link
Owner Author

Cu3PO42 commented Jan 23, 2018

The keys will be stored inside the browser. It provides a database for such use cases.

@robdy
Copy link

robdy commented Jan 23, 2018

Hmm so it's also worth to emphasize that you still need to keep your keys on disk in case you ever wanted to use another browser/machine.

@Cu3PO42
Copy link
Owner Author

Cu3PO42 commented Jan 23, 2018

There will presumably be import/export buttons so that shouldn’t be a concern.

@ddesart
Copy link

ddesart commented May 5, 2018

I like option 2 as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants