IssueRaiser

Self hosting Excalidraw - Umbrella issue

So I'm opening the self-hosting thread. ## Current architecture First an architecture overview. Excalidraw is made of three main parts at the moment. - The client, what you see when you visit `excalidraw.com` which is this repo - The sockets server, which powers the collaboration feature, [it's this repo](https://github.com/excalidraw/excalidraw-room), a Node.js server running `socket.io` - The store server, which powers the sharing feature, [it's this repo](https://github.com/excalidraw/excalidraw-json), a Python server running on GAE with some kind of a DB At the moment, we are planning on publishing a Docker image of the Excalidraw client only. That means that people will be able to self-host the client but they won't be able to use sharing/collaboration features because the client will still have to talk to our cloud-hosted backend servers on which there are CORS restrictions. ## For now For the image that we are planning on publishing soon (in the next few days), we have already stripped out the google tag manager but I see the visible sharing/collaboration icons as an issue. People will be frustrated by not understanding why they don't work. I suggest we strip them out too on the Docker image only. Temporarily until we have a plan for the rest two services. It's the best UX we can offer IMO. ## For the future Moving forward we would like people to be able to self-host a full-fledged Excalidraw environment. My suggestion is to publish a Docker image for each of t

Posted by kbariotis on Jun 15, 2020, 10:21 PM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.3,500 issues0 comments

ux (Sysadmin)

Self hosting Excalidraw - Umbrella issue

kbariotisJun 15, 2020, 10:21 PM

So I'm opening the self-hosting thread. ## Current architecture First an architecture overview. Excalidraw is made of three main parts at the moment. - The client, what you see when you visit `excalidraw.com` which is this repo - The sockets server, which powers the collaboration feature, [it's this repo](https://github.com/excalidraw/excalidraw-room), a Node.js server running `socket.io` - The store server, which powers the sharing feature, [it's this repo](https://github.com/excalidraw/excalidraw-json), a Python server running on GAE with some kind of a DB At the moment, we are planning on publishing a Docker image of the Excalidraw client only. That means that people will be able to self-host the client but they won't be able to use sharing/collaboration features because the client will still have to talk to our cloud-hosted backend servers on which there are CORS restrictions. ## For now For the image that we are planning on publishing soon (in the next few days), we have already stripped out the google tag manager but I see the visible sharing/collaboration icons as an issue. People will be frustrated by not understanding why they don't work. I suggest we strip them out too on the Docker image only. Temporarily until we have a plan for the rest two services. It's the best UX we can offer IMO. ## For the future Moving forward we would like people to be able to self-host a full-fledged Excalidraw environment. My suggestion is to publish a Docker image for each of t

Comments (0)

No comments yet. Start the discussion.

Comment on this issue