Skip to content

Conversation

@hannahbast
Copy link

@hannahbast hannahbast commented Sep 4, 2025

@fnielsen, this is @egonw typing here, this PR started out as "Configure Flask app for proxy deployment" but now has many updates to make Scholia work with QLever. The live instance is shaping up really well. But there is so much here, plz ping me to talk you through the work.

@hannahbast, sorry for updating the title and this description. Since everything was merged into the qlever branch, it all shows up on this PR.

Hannah Bast and others added 2 commits September 4, 2025 12:21
- Add ProxyFix middleware to handle proxy headers correctly
- Configure runserver.py to bind to host 'tajo'
- Fixes CSS/static asset paths when deployed behind proxy

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <[email protected]>
@egonw
Copy link
Collaborator

egonw commented Sep 6, 2025

I wonder if the proxy info can be integrated in the configuration system we have, instead of having it hardcoded.

@fnielsen
Copy link
Collaborator

fnielsen commented Sep 8, 2025

Yes, the hardcoding

I wonder if the proxy info can be integrated in the configuration system we have, instead of having it hardcoded.

Yes, or perhaps the hardcoded variable could be an input variable?

Hannah Bast and others added 26 commits September 20, 2025 00:19
1. Explicitly ask for application/sparql-results+xml (default for Blazegraph)
2. Show QLever exception when available
3. Hack lables by using `REPLACE(STR(?var), ".*/", "") AS ?varLabel`
4. Remove Blazegraph-specific query hints (hint:Query, hint:Prior)
5. Add missing prefix for ASK query and statistics query
1. Add missing PREFIX geof: ... definition
2. Improve error message
3. Hack another SERVICE wikibase:label
1. Automatic pre-formatting using qlue-ls and sed
2. Manual post-correction of all queries (puuh)
added missing prefix
Added OWL prefix to the SPARQL query for better ontology support.
@egonw
Copy link
Collaborator

egonw commented Dec 22, 2025

@fnielsen, I think the branch is in fair shape. I do not have enough experience with Codacy to get the 5 issues fixed. They seem harmless to me (the Markdown ones I do not even get the problem of...).

Anything you like to see improved?

@egonw egonw linked an issue Dec 30, 2025 that may be closed by this pull request
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

Successfully merging this pull request may close these issues.

allotrope panel content broken

8 participants