-
Notifications
You must be signed in to change notification settings - Fork 29
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
PERSEO_CORE_URL set in Dockerfile #810
Comments
Typically, in a docker-compose.yml , you can set PERSEO_CORE_URL in environment section:
|
That's not an option. I need to use the value on The workaround in docker-compose would be to set PERSEO_CORE_URL empty. Also works for k8s. |
Maybe you can contribute with whatever you need in a environment variable and adding it to: https://github.com/telefonicaid/perseo-fe/blob/master/bin/perseo#L170-L173 |
Why not remove it from the Dockerfile? Looks like it's just setting a placeholder value. I don't see what's the point of setting it there. |
PR #811, already merged @pdacostaporto can this issue be closed? |
PERSEO_CORE_URL is set in the Dockerfile. This overwrites the value of
config.perseoCore
fromconfig.js
with a placeholder value (http://corehost:8080
) when running a container.PERSEO_CORE_URL should not be set in the Dockerfile.
If you want to use
config.perseoCore
fromconfig.js
inside a container, the current workaround is to unset PERSEO_CORE_URL or reset it empty.The text was updated successfully, but these errors were encountered: