Skip to content
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

Closed
pdacostaporto opened this issue Oct 30, 2024 · 5 comments
Closed

PERSEO_CORE_URL set in Dockerfile #810

pdacostaporto opened this issue Oct 30, 2024 · 5 comments

Comments

@pdacostaporto
Copy link

pdacostaporto commented Oct 30, 2024

PERSEO_CORE_URL is set in the Dockerfile. This overwrites the value of config.perseoCore from config.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 from config.js inside a container, the current workaround is to unset PERSEO_CORE_URL or reset it empty.

@AlvaroVega
Copy link
Member

Typically, in a docker-compose.yml , you can set PERSEO_CORE_URL in environment section:

environment:
 - PERSEO_CORE_URL=http://iperseo-core-host:8080

@pdacostaporto
Copy link
Author

Typically, in a docker-compose.yml , you can set PERSEO_CORE_URL in environment section:

environment:
 - PERSEO_CORE_URL=http://iperseo-core-host:8080

That's not an option. I need to use the value on config.js.

The workaround in docker-compose would be to set PERSEO_CORE_URL empty. Also works for k8s.

@AlvaroVega
Copy link
Member

AlvaroVega commented Oct 30, 2024

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

@pdacostaporto
Copy link
Author

pdacostaporto commented Oct 30, 2024

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.

@fgalan
Copy link
Member

fgalan commented Oct 31, 2024

PR #811, already merged

@pdacostaporto can this issue be closed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants