openimsdk/openim-docker

[BUG] Regarding the problem that the configuration information modification does not take effect when docker deploys the service

onlyGuo opened this issue · 3 comments

OpenIM Server Version

3.7

Operating System and CPU Architecture

Linux (AMD)

Deployment Method

Docker Deployment

Bug Description and Steps to Reproduce

按照文档 RestfullAPI 对接时,涉及到以secret获取token,处于安全考虑,我修改了容器中config/share.yml的默认secret,保存并重启后,没有生效。

在群里沟通后尝试修改openim-server容器的内建的环境变量IMENV_SHARE_SECRET并重建容器后,问题解决。

但随之而来又出现了一个新的问题,虽然RestfullAPI好使了,但webim端出现了问题,用户登录不进去。按照同样的思路修改openim-chat容器的环境变量CHATENV_SHARE_OPENIM_SECRET后问题解决。

目前不清楚还会不会有其他的问题。

还有一键建议,希望可以在管理员面板中增加一些参数的热更新。比如我在修改webhook.yml时,必须重启容器,如果可以在管理员面板热更新就好了,最好是可以根据不同的callbackCommand配置不同的地址。因为在迭代阶段经常会有这样的场景——一部分业务已经投入生产,但又有一部分业务在开发中,这样单纯的修改webhook的公共地址就会影响线上。目前我在webhook中加了一个中间层解决的这个问题。如果原生支持就更好了。

Screenshots Link

No response

Hello! Thank you for filing an issue.

If this is a bug report, please include relevant logs to help us debug the problem.

Join slack 🤖 to connect and communicate with our developers.

You should modify the OPENIM_SECRET variable in the .env file.

It is recommended to have two separate systems for the testing environment and the production environment, and to deploy them separately rather than mixing them together.