-
Notifications
You must be signed in to change notification settings - Fork 73
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
Collaboration Features Not Working #26
Comments
Any error messages? |
I did just add a STORAGE_URI, and now I'm getting
'redis-cli ping' works. Same default port. |
When I try to get a share link:
When I click 'Live collaboration...' 'Start session' is greyed out. |
I think I'm closer now? back to redis, using auth... redis seems to be configured correctly. I'm using the elastic ip of my ec2 instance in place of localhost (or 0.0.0.0) and there are few/no errors. I can't manage live collaboration, though. Not that I can see. Am I not using room correctly? BTW, I'm visiting the ip directly, as in 1.2.3.4 (after swapping it for localhost in the env/compose files) redis seems prepared to manage scenes etc, but how do I go this crucial step further? |
Live collaboration requires the https protocol, using Nginx |
@yinhuihe is right. |
Trying to get this to work on an Ubuntu 20.04 EC2 instance. I have a subdomain I'd like to use.
docker-compose.yaml
services: frontend: image: excalidraw:v0.1.0-b35a2c3-dirty ports: - 80:80 storage: image: excalidraw-storage-backend:v0.1.0-b35a2c3-dirty restart: always environment: # docs https://github.com/alswl/excalidraw-storage-backend#environement-variables - PORT=8081 ports: - 8081:8081 room: image: excalidraw-room:v0.1.0-b35a2c3-dirty ports: - 8082:80
excalidraw.env.production
Here's my output:
The text was updated successfully, but these errors were encountered: