Add native system support for qlever ui#282
Draft
Qup42 wants to merge 3 commits intoqlever-dev:mainfrom
Draft
Conversation
When `UI_SYSTEM = native`, the UI is started with `qlever-ui dev <port>` instead of a container, config is managed via `qlever-ui manage config`, and stopping kills the native process rather than a container. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Extraction of config to go
hannahbast
requested changes
May 6, 2026
Collaborator
hannahbast
left a comment
hannahbast
left a comment
There was a problem hiding this comment.
@Qup42 Thanks a lot! We tried this and it worked. Two things:
- There was a problem with the
ALLOWED_HOSTS qlever ui --stopworks fordockerbut not fornative
Collaborator
Author
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Yet to test it though.