Helm Chart: NEXT_PUBLIC_BASE_PATH and NEXT_PUBLIC_SIGN_UP_DISABLED environment variables not respected

[shaunhavelaarx]

Description

The Helm chart installation does not properly configure the base path when setting the NEXT_PUBLIC_BASE_PATH environment variable. This prevents the application from being served at the specified base path.

The Helm chart installation does not properly configure the sign up process when setting the NEXT_PUBLIC_SIGN_UP_DISABLED environment variable. The UI still allows you to se this up even though the Sign up env var is set to disabled.

Current Behavior

When installing Langfuse using Helm with a custom NEXT_PUBLIC_BASE_PATH environment variable set, the application still serves content at the root path instead of the specified base path.

Expected Behavior

The application should serve all content at the path specified in NEXT_PUBLIC_BASE_PATH when this environment variable is set during Helm installation.

Steps to Reproduce

1. Add the Langfuse Helm repository
2. Create a values.yaml file with the following configuration:

env:
  NEXT_PUBLIC_BASE_PATH: "/langfuse"
  NEXT_PUBLIC_SIGN_UP_DISABLED: "true"

3. Access the application

Environment

• Langfuse Helm chart version: [0.10.0]

Additional Context

This configuration is important for scenarios where Langfuse needs to be served under a sub-path, such as when using an ingress controller with path-based routing.

[dosubot]

Hey @shaunhavelaarx! 👋 I'm here to help you with bugs, questions, and becoming a contributor. Let's tackle this issue together!

The issue you're experiencing with the NEXT_PUBLIC_BASE_PATH environment variable not being respected in the Helm chart might be due to the Helm chart not having specific configurations or templates that handle this variable. Based on the available information, there is no documentation or configuration in the Helm chart that specifically addresses the use of NEXT_PUBLIC_BASE_PATH for path configuration ^[1][2].

To address this, you might need to manually adjust the application or web server configuration to ensure it respects the NEXT_PUBLIC_BASE_PATH. This could involve modifying the deployment templates or scripts to include logic that handles this environment variable correctly.

If the Helm chart or application does not natively support this configuration, consider reaching out to the maintainers or checking if there are any updates or community solutions that address this specific need.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}

[shaunhavelaarx]

Just to clarify, I did edit the deployment file and manually added the NEXT_PUBLIC_BASE_PATH and NEXT_PUBLIC_SIGN_UP_DISABLED env variables, but they are not being applied

[Steffen911]

@shaunhavelaarx Have you tried to use langfuse.additionalEnv which one should use to provide additional environment variables as documented in our Readme?

Keep in mind that you have to build the images yourself and also need to overwrite the NEXTAUTH_URL as discussed in https://langfuse.com/self-hosting/custom-base-path.