Custom base path with prebuilt image

[szwedum]

Describe the feature or potential improvement

Currently running langfuse with custom base path only after building web container image from source with env variable NEXT_PUBLIC_BASE_PATH. However, this rises issues with versioning and using stable and safe source for running langfuse on production. Would it be possible to have a new feature, so that a custom base path can be configured with prebuilt image?

Additional information

No response

[Steffen911]

@szwedum Unfortunately the custom base path must be part of the static frontend sources to apply correctly which means that it must be injected at build time. Therefore, we cannot provide pre-build images that support a custom base path.

[szwedum]

@Steffen911
Thanks for the clarification on the technical limitations of NEXT_PUBLIC_BASE_PATH. I understand pre-built images with custom paths aren't feasible. Would it be possible to provide an official Dockerfile with build ARGs in the repository? This would help users like me who need custom base paths by:

1. Providing an officially maintained build process
2. Documenting the exact build steps you recommend
3. Making it easier to integrate into CI/CD pipelines

Something like:
dockerfile

ARG NEXT_PUBLIC_BASE_PATH="" ARG NEXTAUTH_URL # ... rest of build process
This way, users can build their own images consistently without having to reverse-engineer the build process. Would this be something the team could add to the repo?

[Steffen911]

@szwedum The docker image already has the args: https://github.com/langfuse/langfuse/blob/main/web/Dockerfile#L57. Is the request mainly about documentation on how to build the image or should we also change things in the image structure and layout per your suggestion?