-
Notifications
You must be signed in to change notification settings - Fork 11
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
WSGI invocation fails #585
Comments
That's not a use that I've experimented with. I've also never tried to deploy it with apache, so take this with a grain of salt. The Blawx source code doesn't package the code as a module for use by other Python code on the same system. I suspect that the problem is that Blawx is not "installed" as a Python module, so the namespace is only available to Python scripts running in the root folder of the project. Blawx doesn't have a setup.py file to facilitate installing it, or anything along those lines, and it's beyond my current capacity to build one at the moment. You could create one and install it that way, or use any of the other methods like moving the code into site packages for the python interpreter, or adding the location of the Blawx code to the python search path. I presume you are doing this inside a revised docker container based on the existing Dockerfile. Otherwise Blawx will not have access to the Prolog dependencies even if you manage to import it into your code. I can't promise that there aren't other issues that arise when using Blawx as a Python module. Off the top of my head, it wouldn't surprise me if you needed to change how some of the imports are written. But I'd be happy to look at a PR for whatever you get working. |
I've had to dive deep on this; there are references to absolute paths all through both the server and client-side code. I've brute-forced my immediate need, but hope to be able to post a PR for this eventually. |
Hi there - I have need to deploy blawx at a URL offset from the root of the server. The usual way to do this in django is to run it in a WSGI container with an offset, but when I invoke the existing wsgi.py using such a mapping, (after installing all the requirements) I get the following:
The text was updated successfully, but these errors were encountered: