Registry 3.0 ENV variables #5192
-
I'm really sorry for the dumb question but I did not find a solution for running V3 on remote server. Thanks in advance |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Hi @ottuzzi-at-vegans - no worries, we need to update our documentation for 3.0 to make everything easier. We have a table of ENV vars for 3.0, but not yet published. For now, let me just explain. :) The UI container image needs to be configured with the location of the API component. For all other config options, the UI will load the values from the API component. As a result, the only config option you should use for the UI container is:
Where the value should be the URL of the API component's REST API. For example:
|
Beta Was this translation helpful? Give feedback.
Hi @ottuzzi-at-vegans - no worries, we need to update our documentation for 3.0 to make everything easier. We have a table of ENV vars for 3.0, but not yet published. For now, let me just explain. :)
The UI container image needs to be configured with the location of the API component. For all other config options, the UI will load the values from the API component. As a result, the only config option you should use for the UI container is:
REGISTRY_API_URL
Where the value should be the URL of the API component's REST API. For example:
https://registry-api.example.org/apis/registry/v3