-
Task
-
Resolution: Done
-
Critical
-
None
-
1.2.1
-
3
-
False
-
-
False
-
-
-
RHDH Docs Team 3259
There might be simpler way to express step 3. II in https://docs.redhat.com/en/documentation/red_hat_developer_hub/1.2/html/administration_guide_for_red_hat_developer_hub/assembly-install-rhdh-ocp#proc-add-custom-app-config-file-ocp-operator_assembly-install-rhdh-ocp
In the code block, use a simpler user replaceable value: `https://<rdhd-url>` rather than: `https://backstage-<custom_resource_name>-<namespace_name>.<openshift_ingress_domain>`
In the note: "Replace <rhdh-url> by your Red Hat Developer Hub instance." rather than
Set the external URL of your Red Hat Developer Hub instance in the app.baseUrl, backend.baseUrl and backend.cors.origin fields of the application configuration. By default, the URL is similar to the following example: https://backstage-<custom_resource_name>-<namespace_name>.<openshift_ingress_domain>;.
Note
You can use the oc get ingresses.config/cluster -o jsonpath='
{.spec.domain}' command to display your ingress domain. If you want to use a different host or sub-domain, customize the CR spec.application.route field and adjust the application configuration accordingly.
And remove the note as the procedure is focused on using the OCP UI rather than CLI.
- is related to
-
RHIDP-3037 [DOC] Convert 27/6/24 test day results spreadsheet to jiras
- Closed
- links to