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

Automated update #56

Open
bbogdanov opened this issue Sep 22, 2020 · 4 comments
Open

Automated update #56

bbogdanov opened this issue Sep 22, 2020 · 4 comments
Labels
enhancement New feature or request

Comments

@bbogdanov
Copy link
Collaborator

The problem

Currently, the update to the newer available version happens almost manually and It will be great to have a way to automatically update to newer versions.

At the moment the process is 50% automated 50% manual.

Expected behavior

Having a one click way to update to the newer available version.

Blockers

By using the browser we are blocked from reaching the file system of the computer running the web server.
We can contact the BE guys and find out a way if they are willing to provide a endpoint that based on the provided URL can download a zip and replace the files inside the zip in the provided folder of the alternative UI. We can easily get the latest release zip URL thanks to GitHub api.

Visual example

Your image title

@bbogdanov bbogdanov added the enhancement New feature or request label Sep 22, 2020
@bbogdanov bbogdanov added this to Ideas for approval in Development board Sep 22, 2020
@CzBiX
Copy link
Owner

CzBiX commented Sep 22, 2020

Related #57 .
If it's implemented, we no longer need to manual upgrade any more.

@bbogdanov
Copy link
Collaborator Author

How do you see the connection between qb running on the client server and the website running on different server?

I understand the CORS idea and I see the flow like this:
Going to website => Dialog pops up for server location => Providing server URL => Login => Continue using the UI

@CzBiX
Copy link
Owner

CzBiX commented Sep 22, 2020

@bbogdanov Right.
The users have to change CORS settings in qb first.

@bbogdanov
Copy link
Collaborator Author

From my prespective as a user, this will be a little frustrating when using a new device and have to go through the entire flow I mentioned in the comment above. I believe we can find a much better way to resolve the update issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Development board
  
Ideas for approval
Development

No branches or pull requests

2 participants