自己部署的Lobe版本，新的AI Provider无法展示，仍然是老版本的视图

[zhufeizzz]

📦 部署环境

Docker

📌 软件版本

v1.51.13

💻 系统环境

Windows

🌐 浏览器

Chrome

🐛 问题描述

已经升级到最新版本了，但是AI Provider的视图仍然是老版本的，无法查看新版本视图。

如果登录Lobe官方地址，新的AI Provider视图是可以展示的。

📷 复现步骤

No response

🚦 期望结果

No response

📝 补充信息

No response

[lobehubbot]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

📦 Deployment environment

Docker

📌 Software version

v1.51.13

💻 System environment

Windows

🌐 Browser

Chrome

🐛 Question description

It has been upgraded to the latest version, but the view of AI Provider is still the old version and the new version of the view cannot be viewed.

If you log in to the official Lobe address, the new AI Provider view can be displayed.

📷 Reproduction steps

No response

🚦 Expected results

No response

📝 Supplementary information

No response

[lobehubbot]

👀 @zhufeizzz

Thank you for raising an issue. We will investigate into the matter and get back to you as soon as possible.
Please make sure you have given us as much context as possible.
非常感谢您提交 issue。我们会尽快调查此事，并尽快回复您。 请确保您已经提供了尽可能多的背景信息。

[dosubot[bot]]

To resolve the issue where the new AI Provider views are not displaying after upgrading your self-hosted Lobe Chat application, you can follow these steps:

1. Ensure the Latest Docker Image is Used: Make sure you have pulled the latest Docker image for Lobe Chat. You can do this by running:

   docker pull lobehub/lobe-chat

2. Restart the Docker Container: Stop and remove the existing container, then start a new one with the latest image:

   docker stop lobe-chat
   docker rm lobe-chat
   docker run -d -p 3210:3210 \
     -e OPENAI_API_KEY=sk-xxxx \
     -e OPENAI_PROXY_URL=https://api-proxy.com/v1 \
     -e ACCESS_CODE=lobe66 \
     --name lobe-chat \
     lobehub/lobe-chat

3. Check Configuration Files: Verify that your configuration files, especially src/config/modelProviders/index.ts, are correctly set up to include the new AI Providers. This file controls which providers are available and visible in the application ^[1].

4. Run Migration Scripts: Ensure that any necessary migration scripts have been executed to update the database schema and data. This includes scripts for updating UI components and configurations ^[2].

These steps should help in displaying the new AI Provider views in your self-hosted Lobe Chat application.

To continue talking to Dosu, mention @dosu.

---

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

[hedeqiang]

railway 部署相同的问题

[lobehubbot]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

The same issue with railway deployment

[sxjeru]

添加环境变量 NEXT_PUBLIC_CLIENT_DB=pglite 有用吗，可以试试。

[lobehubbot]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

Is adding the environment variable NEXT_PUBLIC_CLIENT_DB=pglite useful? You can try it.

[hedeqiang]

添加环境变量 NEXT_PUBLIC_CLIENT_DB=pglite 有用吗，可以试试。

没效果，已经添加了

[arvinxx]

你需要从头构建docker镜像

[wangfeng35]

添加环境变量 NEXT_PUBLIC_CLIENT_DB=pglite 有用吗，可以试试。

这个目前只有在自己build docker镜像阶段生效 等2.0版本吧

[lobehubbot]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

Is the environment variable NEXT_PUBLIC_CLIENT_DB=pglite useful? You can try it.

This is currently only available in the build docker image stage and will wait for version 2.0

[arvinxx]

本地数据库之前的 db 方案是 dexie，导致没法和云端数据库版本对齐，因此现在客户端的 docker 镜像还是用的老的 settings/llm 页面。

而新的客户端数据库版本会采用 pglite 作为本地数据库，几乎可以完全对齐 postgres 的能力，因此未来的客户端版本也会使用新的 provider 页面。而为了现行验证这个方案的可行性，我们的社区预览版（https://chat-preview.lobehub.com ）已经先行迁到了 pglite 中做验证。目前稳定运行了快2个月，也收集到了不少反馈。

由于客户端数据库的迁移会是个很大的 Breaking Change，因此这部分工作将会在 LobeChat V2 中完成。

等 V2 发布，我们的客户端数据库版本将能完全对齐云端数据库版本的功能（包括知识库与向量检索）。而现在还在做最后的数据一键导出和一键迁移 pglite 功能的开发 （#5581 ），确保 V1 的客户端数据库版本的用户能无缝升级到 V2

[lobehubbot]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

The db solution before the local database was dexie, which caused it to be unable to align with the cloud database version. Therefore, the docker image of the client is still using the old settings/llm page.

The new client database version will use pglite as the local database, which can almost fully align postgres, so future client versions will also use the new provider page. In order to verify the feasibility of this solution in the current way, our community preview version (https://chat-preview.lobehub.com) has been moved to pglite for verification. Currently, it has been running steadily for almost 2 months and has collected a lot of feedback.

Since the migration of the client database will be a large Breaking Change, this part of the work will be done in LobeChat V2.

After V2 is released, our client database version will be able to fully align with the functions of the cloud database version (including knowledge base and vector retrieval). And now we are still doing the development of the last data one-click export and one-click migration function (#5581) to ensure that the user of the client database version of V1 can be disabled Upgrade to V2