-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
无法保存到后端数据库。如果问题持续存在,您应该保存文件到本地,以确保您的工作不会丢失。 #41
Comments
version: "3.8" services: excalidraw-storage-backend: excalidraw-room: redis: |
可以直接改成mysql://用户名:密码@localhost:3306吗 |
你使用的镜像都不是我提供的,是不是找错了仓库了? |
services: storage: room: redis: |
你可以查看 https://github.com/alswl/excalidraw-storage-backend 源码。另外参考 https://github.com/jaredwray/keyv 如何使用 MySQL 连接。 |
你的mysql都不在这个网桥组里,那肯定不能通过主机名去访问呀。 |
请教一下,那我要想存在本地的mysql数据库应该怎么改呢 |
STORAGE_URI=mysql://root:sjl.0927@localhost:3306 |
|
我没用mysql,我用的mongodb,保存也仅仅是以文件方式保存到客户端的本地。 |
我也遇到,偶尔发生这种问题,一般是在和远程共享白板协作过程中 |
@alswl help! 我也遇到的这个问题。只要协作就会出现。用的也是大佬的镜像。 services:
frontend:
image: alswl/excalidraw:v0.17.3-fork-b1
environment:
- VITE_APP_BACKEND_V2_GET_URL=https://10.35.144.14:2086/api/v2/scenes/
- VITE_APP_BACKEND_V2_POST_URL=https://10.35.144.14:2086/api/v2/scenes/
- VITE_APP_WS_SERVER_URL=https://10.35.144.14:2087
- VITE_APP_FIREBASE_CONFIG={}
- VITE_APP_HTTP_STORAGE_BACKEND_URL=https://10.35.144.14:2086/api/v2
- VITE_APP_STORAGE_BACKEND=https
ports:
- 7080:80
storage:
image: alswl/excalidraw-storage-backend:v2023.11.11
restart: always
environment:
# docs https://github.com/alswl/excalidraw-storage-backend#environement-variables
- PORT=8081
- STORAGE_URI=pg://excalidraw:[email protected]:5432/exca
ports:
- 8081:8081
room:
image: excalidraw/excalidraw-room:sha-49bf529
ports:
- 8082:80 使用了https反代,postgre数据库。目前只要一协作就报无法保存到数据库。 excalidraw-storage-backend容器报这个错误:
|
经过一番折腾,发现不使用https,而使用localhost,是可以使用的。那么就是经过https反代就出现了问题。后来参考大佬的https://github.com/alswl/excalidraw-collaboration/tree/master/advanced-nginx 终于成功了。 |
通过 redis 然后可以正常解决,然后通过域名使用 https 正常使用。可以有偿协助部署 , 邮箱: st09100#126.com |
The text was updated successfully, but these errors were encountered: