We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I'm using the helm chart and I modified only the ingress part to be publish it on my server
ingress: enabled: true annotations: cert-manager.io/cluster-issuer: letsencrypt-http01-prod nginx.ingress.kubernetes.io/proxy-buffer-size: "128k" hosts: - host: geonetwork.myhost.com paths: - "/datahub" tls: - secretName: geonetwork-myhost-com-key-pair hosts: - geonetwork.myhost.com className: "external-nginx"
The application starts and it's available using https://geonetwork.myhost.com/datahub but in the homepage I receive an error
An error was received Http failure response for https://geonetwork.myhost.com/geonetwork/srv/api/me: 404 Not Found
Is there some additional configuration in this chart that can be used to manage the relative path?
The text was updated successfully, but these errors were encountered:
Ok I found the required settings
extra_environment: - name: GN4_API_URL value: "https://geonetwork.myhost.com/mycustomservice/geonetwork/srv/api"
Sorry, something went wrong.
hello, I think we probably need to add the support for this configuration because it's a major parameter for having datahub functioning.
I have created an issue: #5
No branches or pull requests
I'm using the helm chart and I modified only the ingress part to be publish it on my server
The application starts and it's available using https://geonetwork.myhost.com/datahub but in the homepage I receive an error
An error was received
Http failure response for https://geonetwork.myhost.com/geonetwork/srv/api/me: 404 Not Found
Is there some additional configuration in this chart that can be used to manage the relative path?
The text was updated successfully, but these errors were encountered: