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

FEATURE: Load/Save settings from/to server #494

Open
quintesse opened this issue Jun 22, 2018 · 4 comments
Open

FEATURE: Load/Save settings from/to server #494

quintesse opened this issue Jun 22, 2018 · 4 comments

Comments

@quintesse
Copy link

quintesse commented Jun 22, 2018

Right now setting up several clients/browsers is quite a hassle. Yes you can save all the settings as files but then you still have to get them to the other clients.

Right now I have to:

  1. Save the files
  2. Locate them
  3. Mail them
  4. Save them locally
  5. Load them

And you'd have to do that each time you make any changes (or remember to make the exact same changes everywhere).

Being able to save the settings on the server itself somehow would be very useful I think.

This issue would be for the necessary UI changes. (Would there be extra buttons for all the load/save options that currently exist, or is there a nicer/smarter way to handle this?)

Needs LaserWeb/lw.comm-server#62 for the supporting server-side API.

@jorgerobles
Copy link
Collaborator

Hmm could be done thru https://www.npmjs.com/package/google-drive but it's not work of an evening or two :P

@quintesse
Copy link
Author

Isn't there a way it could be done on the server itself?

@jorgerobles
Copy link
Collaborator

jorgerobles commented Jun 23, 2018

Ok, I misunderstood. You mean to use have lw.comm-server store the settings, while running the server standalone, and not as desktop app isn't it?

If so, please open the issue at https://github.com/LaserWeb/lw.comm-server, thanks. This repo is meant to the UI part.

@quintesse
Copy link
Author

I opened LaserWeb/lw.comm-server#62 and updated the description of this issue somewhat.

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

No branches or pull requests

2 participants