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

Implicitly set BACKEND_HOSTNAME env var for backend url in frontend if backend ingress is enabled #37

Open
JuniorJPDJ opened this issue Jul 10, 2023 · 0 comments
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@JuniorJPDJ
Copy link
Contributor

JuniorJPDJ commented Jul 10, 2023

Describe the solution you'd like

Everything is actually in the title ;)
This would allow people to not set env var by themselves when deploying whole piped.

Additional Information

No response

@JuniorJPDJ JuniorJPDJ added the enhancement New feature or request label Jul 10, 2023
@JuniorJPDJ JuniorJPDJ changed the title [piped] Implicitly set env var for backend url in frontend if backend ingress is enabled [piped] Implicitly set BACKEND_HOSTNAME env var for backend url in frontend if backend ingress is enabled Jul 10, 2023
@samip5 samip5 added the help wanted Extra attention is needed label Aug 21, 2023
@samip5 samip5 changed the title [piped] Implicitly set BACKEND_HOSTNAME env var for backend url in frontend if backend ingress is enabled Implicitly set BACKEND_HOSTNAME env var for backend url in frontend if backend ingress is enabled Nov 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants