-
Notifications
You must be signed in to change notification settings - Fork 208
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/move server frontend mapping to the frontend #591
Feature/move server frontend mapping to the frontend #591
Conversation
9ac3f68
to
382adf7
Compare
382adf7
to
cac6b75
Compare
14bd291
to
17c2a15
Compare
server/src/main/kotlin/suwayomi/tachidesk/server/util/WebInterfaceManager.kt
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@schroda Is this ready to be merged? WebUI has the mapping?
c258adf
to
96bc901
Compare
not yet, I'll ping you when it's ready I updated the automated webUI update check to use the "HAScheduler" |
96bc901
to
891cd73
Compare
891cd73
to
531705d
Compare
I added a function to get the latest version of the webUI preview, instead of having to change the naming pattern of the bundled webUI zip file from |
webUI repo is up-to-date |
Currently the webUI requires a server release.
This PR enables the webUI to do its own releases by adding the functionality to the server to download the latest webUI version.
The webUI defines which webUI version is compatible with which server version.
Thus, the server can download the latest compatible version based on its version.
The mapping of webUI version to server version is a file inside the webUI repo.
This file gets updated each time a new webUI version gets released which requires a newer server version than the previous release.
example:
In this example
This does not change the current behaviour of the server release bundling a webUI version.
This version is still used as a fallback in case everything else fails.
How the server will setup the webUI:
download result handling:
Support for different webUIs is also added.
As long as they fullfill the required conditions, e.g. version mapping file in correct format, available version downloads, they can be defined in the server to be provided as an optional webUI that can be used.
In case the server runs into issues with one of these webUIs (e.g. download not possible) it will fallback to the default webUI