Skip to content

Commit

Permalink
docs: clarify prod branch when building own image
Browse files Browse the repository at this point in the history
  • Loading branch information
marcklingen committed Sep 16, 2024
1 parent 0144c8a commit f704469
Showing 1 changed file with 14 additions and 2 deletions.
16 changes: 14 additions & 2 deletions pages/docs/deployment/self-host.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -238,9 +238,15 @@ While we recommend using the prebuilt docker image, you can also build the image
The repo includes multiple `Dockerfile` files. You only need to build the `web` Dockerfile as shown below.

```bash
# clone repo
git clone https://github.com/langfuse/langfuse.git
cd langfuse
git checkout production # main branch includes unreleased changes that might be unstable

# checkout production branch
# main branch includes unreleased changes that might be unstable
git checkout production

# build image
docker build -t langfuse/langfuse -f ./web/Dockerfile .
```

Expand All @@ -260,9 +266,15 @@ NEXTAUTH_URL="https://yourdomain.com/langfuse-base-path/api/auth"
Build image with `NEXT_PUBLIC_BASE_PATH` as build argument:

```bash /NEXT_PUBLIC_BASE_PATH/
# clone repo
git clone https://github.com/langfuse/langfuse.git
cd langfuse
git checkout production # main branch includes unreleased changes that might be unstable

# use production branch
# main branch includes unreleased changes that might be unstable
git checkout production

# build image with NEXT_PUBLIC_BASE_PATH
docker build -t langfuse/langfuse --build-arg NEXT_PUBLIC_BASE_PATH=/langfuse-base-path -f ./web/Dockerfile .
```

Expand Down

0 comments on commit f704469

Please sign in to comment.