-
Notifications
You must be signed in to change notification settings - Fork 8
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
Apache needs hostname set to "ood" #1
Comments
Since OnDemand uses Software Collections for Apache the generated config is at |
Ah ok, so what modification do I need to do exactly? |
It does indeed look like if you would execute |
If you aren't going to modify the Apache config ood-portal.conf directly, I wonder what the ramifications would be in executing |
Hmm I'm not sure if something has changed, but I'm getting an error that the package isn't signed:
|
I'm not sure what has changed (nothing afaik) but should I use a different one? https://yum.osc.edu/ondemand/latest/ |
I'll just use |
I think my colleague recently built a new rpm for 1.6 built failed to properly sign it and is in the process of fixing that - this might be the error you saw. Though the rpm you are using I think is the final release candidate for 1.6, we need to upload a properly signed rpm. FWIW https://yum.osc.edu/ondemand/latest/ is what we use at OSC, but of course its less stable because its easier for us to push out a quick fix to respond to OSC user feedback. https://yum.osc.edu/ondemand/1.6/ will eventually have a copy of the stable signed release though it doesn't yet (it has 1.6.1 and I dont recall the state of that). Most sites have https://yum.osc.edu/ondemand/1.5/ installed right now. |
Okay cool, thanks for the details! I did get the server name to update, but of course using the docker hostname (and having it switch on my host) doesn't work. I'd need to identify ood as a hostname on my host too, which is probably harder than just getting the ip address from the log. So until there is a better solution, I'm going to leave it commented out. I'm building on the base container recipe for the VNC dependencies for the nodes, for interactive apps. This is where it will likely get tricky... we'll see! |
Good luck |
I figured it would be in the portal configuration file, but setting:
Didn't seem to do anything. So we need a solution to this message - specifically, where is the apache.conf file (it's not in the traditional spot) and then what's the best way to change it.
The text was updated successfully, but these errors were encountered: