-
Notifications
You must be signed in to change notification settings - Fork 107
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
Issues in spinning up report portal instance in OpenShift. #3426
Comments
Hello @X261959 ! Please let us know if this helps. |
|
Hi @AmsterGet We haven't heard back from you ? Could you please suggest something here over this. |
@X261959 What is your |
@HardNorth I ain't sure how much this will be of help to us at this point, as we are facing issues with our routes in open-shift. Could you please suggest something from routes perspective ? |
@X261959 I don't have working OpenShift example right now, so I can't suggest here anything, sorry. |
Hello ReportPortal team,
We are currently working on spinning up an RP portal instance in our environment in OpenShift.
The key difference between our setup and the default Ingress way is that we have an NGINX proxy server in front of our cluster.
The location in the NGINX server dedicated to the RP instance is /rpportal, which proxies all the requests to OS Routes. Due to this /ureport location, all the routes in the frontend app should also have a /rpportal prefix.
We tried to define a "homepage" property in the package.json file, and manually specify this prefix in the routes inside of the /app/src/routes/routesMap.js file.
Unfortunately it did not work - we keep getting HTTP codes 302 and 307 when we access the UI.
Can you let us know of the correct procedure to define a url prefix in the code?
The text was updated successfully, but these errors were encountered: