langfuse / langfuse/oss-llmops-stack

trouble setting this up

Open
#9 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
152
Forks
8
PR merge metrics
No merged PRs in 30d

Description

Hello there,
Thanks for this nice repository.
I assume this is for novices like me.
The problem I have when setting this up:
Set 1: Setup langfuse: I am trying to get this to run in my docker NAS synology. Following the video is straight forward, but I get the folloing issues:

langfuse-langfuse-worker-1  | 2025-02-23T13:59:30.065Z error    Error running background migrations
langfuse-langfuse-worker-1  | Invalid `prisma.backgroundMigration.findFirst()` invocation:
langfuse-langfuse-worker-1  |
langfuse-langfuse-worker-1  |
langfuse-langfuse-worker-1  | The table `public.background_migrations` does not exist in the current database.
langfuse-langfuse-worker-1  | PrismaClientKnownRequestError:
langfuse-langfuse-worker-1  | Invalid `prisma.backgroundMigration.findFirst()` invocation:
langfuse-langfuse-worker-1  |
langfuse-langfuse-worker-1  |
langfuse-langfuse-worker-1  | The table `public.background_migrations` does not exist in the current database.
langfuse-langfuse-worker-1  |     at Bn.handleRequestError (/app/node_modules/.pnpm/@prisma+client@6.3.0_prisma@6.3.0_typescript@5.4.5__typescript@5.4.5/node_modules/@prisma/client/runtime/library.js:121:7362)
langfuse-langfuse-worker-1  |     at Bn.handleAndLogRequestError (/app/node_modules/.pnpm/@prisma+client@6.3.0_prisma@6.3.0_typescript@5.4.5__typescript@5.4.5/node_modules/@prisma/client/runtime/library.js:121:6686)
langfuse-langfuse-worker-1  |     at Bn.request (/app/node_modules/.pnpm/@prisma+client@6.3.0_prisma@6.3.0_typescript@5.4.5__typescript@5.4.5/node_modules/@prisma/client/runtime/library.js:121:6393)
langfuse-langfuse-worker-1  |     at async l (/app/node_modules/.pnpm/@prisma+client@6.3.0_prisma@6.3.0_typescript@5.4.5__typescript@5.4.5/node_modules/@prisma/client/runtime/library.js:130:9645)
langfuse-langfuse-worker-1  |     at async db_1.prisma.$transaction.maxWait (/app/worker/dist/backgroundMigrations/backgroundMigrationManager.js:34:39)
langfuse-langfuse-worker-1  |     at async Proxy._transactionWithCallback (/app/node_modules/.pnpm/@prisma+client@6.3.0_prisma@6.3.0_typescript@5.4.5__typescript@5.4.5/node_modules/@prisma/client/runtime/library.js:130:8012)
langfuse-langfuse-worker-1  |     at async /app/worker/dist/backgroundMigrations/backgroundMigrationManager.js:32:17
langfuse-langfuse-worker-1  |     at async /app/packages/shared/dist/src/server/instrumentation/index.js:41:28
langfuse-langfuse-worker-1  |     at async BackgroundMigrationManager.run (/app/worker/dist/backgroundMigrations/backgroundMigrationManager.js:29:9)
langfuse-langfuse-worker-1  | 2025-02-23T13:59:30.066Z error    prisma:error
langfuse-langfuse-worker-1  | Invalid `prisma.$queryRaw()` invocation:
langfuse-langfuse-worker-1  |
langfuse-langfuse-worker-1  |
langfuse-langfuse-worker-1  | Raw query failed. Code: `42P01`. Message: `relation "prices" does not exist`
langfuse-langfuse-worker-1  | 2025-02-23T13:59:30.067Z error    Error upserting default model prices after 3852ms:
langfuse-langfuse-worker-1  | Invalid `prisma.$queryRaw()` invocation:
langfuse-langfuse-worker-1  |
langfuse-langfuse-worker-1  |
langfuse-langfuse-worker-1  | Raw query failed. Code: `42P01`. Message: `relation "prices" does not exist`

After that it starts a fairly lenghy migration process.
And then it shows the following:
langfuse-langfuse-web-1 | - Local: http://343d081f70ed:3000

I can access it with localhost from my other machine, this is nice!

So on to step 2! Setup LiteLLM Proxy: but how do I do this?
I didn't install litellmproxy yet. I see langfuse is the main driver behind this. But it would be awesome to have really all steps laid out clearly

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the setup video and the Docker deployment described in the issue, then reproduce the worker output on a Synology NAS. Document the complete path from Langfuse startup through LiteLLM Proxy setup, with migrations completing and both services accessible.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker
Domain
devops, documentation, infrastructure
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.