Open Source Self-Hosting Appears Unusable #7890
-
|
I cloned the repo and ripped out the ee/ code, SSO, UI customizations and so on. Now, when I attempt to perform first-time setup, I:
at step 4, I receive an error: Is it intended that creating a project is EE scope? It seems the app is unusable if we can't do this iiuc. edit: I think this isn't intended based on https://github.com/orgs/langfuse/discussions/7144 |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
Hi @Vandivier, After the update where we open sourced all product features (blog), there are a couple of remaining enterprise APIs that require a license. If you want to run Langfuse OSS, you can run the published container images (see self-hosting docs) or built from source as long as you do not provide a license key. This will make sure that none of the non-FOSS features are available which are located in the /ee folders. In this example specifically We'd love to offer a way to completely eject this non-FOSS code from the repo, however, this currently breaks the imports within the monorepo setup. We are very open for contributions on this. I think a good role model here could be https://github.com/PostHog/posthog-foss which is a read-only mirror of the main posthog repo but ejects the ee code. |
Beta Was this translation helpful? Give feedback.
Hi @Vandivier,
After the update where we open sourced all product features (blog), there are a couple of remaining enterprise APIs that require a license.
If you want to run Langfuse OSS, you can run the published container images (see self-hosting docs) or built from source as long as you do not provide a license key. This will make sure that none of the non-FOSS features are available which are located in the /ee folders.
In this example specifically
@/src/ee/features/admin-api/server/projects/createProjectis imported inweb/src/pages/api/public/projects/index.tswhich includes a check whether the admin-api is available (permalink) before the ee code gets executed.We'd love to offer a…