-
Notifications
You must be signed in to change notification settings - Fork 27
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
Hosting MegaQC as one of many applications rather than as the default #428
Comments
I remember this being a bit annoying to do. I would try setting the environment variable - DB_NAME=${DB_NAME}
- DB_USER=${DB_USER}
- DB_PASS=${DB_PASS}
+ - SCRIPT_NAME=/megaqc
db:
image: postgres:latest
volumes: |
I've used just the docker image, with a non-docker database, rather than docker compose. If I set that going (i.e. docker run) with SCRIPT_NAME as an environment variable, should that work? |
I believe you need |
This seems to make it so that e.g. 0.0.0.0/megaqc takes me to a 404 landing page, but doesn't move all the urls behind /megaqc |
I think what I'm looking for is some way of essentially adding a |
|
Hmm ok this does work on my laptop, but not on the server. There must be something interfering with it. If I Could the nginx reverse proxy on the server be messing with this (I'm not very familiar with how they work), or do you think it's likely to be something else? |
I am currently hosting MegaQC via the docker container on a RHEL8 server. I.e. navigating to the server's IP brings up the MegaQC interface.
I would like to change this set-up so that navigating to the server's IP takes me to a homepage from which I can then navigate either to MegaQC or some other application. We're currently using nginx for this elsewhere. What do I need to configure or change (on the MegaQC side of things) in order to host at e.g.
IP/megaqc/
rather than justIP/
?The text was updated successfully, but these errors were encountered: