-
Notifications
You must be signed in to change notification settings - Fork 10
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
Current issues with the dev version | Best way to support you bringing this forward? #9
Comments
Now as I was playing around with your repo a bit these are my results: My setup:
My findings:
The chi middleware responds with error 404 here.
This is an example request being sent while uploading a file:
If I can be of any help with any of these issues please let me know 😎 |
I currently lack a clear understanding of which stubs or functionality we need to re-implement from the Firebase API. This could potentially be a significant time-sink. I still prefer not to modify any frontend code and instead focus on providing correct request/response handling for all fetches. My goal is to eventually enable easy self-hosting on AWS Fargate. However, I must admit, I am not super keen in extensive programming during my spare time at the moment. The backend storage issue, i don't get. It works for me with link sharing using S3. Interestingly, I didn't know that one can embed arbitrary images 🙈. That's news to me. |
Totally agree with that. Unfortunately I never used Firebase before so I can't provide any help either. Maybe I get a better understanding while diving deeper into the code. What I can say is that there is a working (but outdated) fork out there where the upstream code was modified so a httpStorage backend can be used instead of Firebase. This is the repository: https://github.com/squatica/excalidraw
OK I won't use any Amazon services so this is where I'm out 😉 Anyway – I'm sure your approach is so great that we can evolve it so it's becoming an alternative to the current (code modifying) forks. Maybe I can find some other Go contributors who can help here 🙏
Could you maybe try if the backend also works without S3? I'm using an sqlite db at the moment and will try it with the directory storage today.
Yes, that's one of the greatest features apart from already being a great piece of software at all 😎 |
Hey @PatWie , This is great work, I really appreciated. One issue that I got is even I set (before starting the
the app seems doesn't use it. Although I can see Also is the the popup |
To troubleshoot reported issues, we add more debugging outputs in the logging. This includes detailed, structured logs in the Create and FindID methods to provide better traceability and debuggability. These changes help diagnose issues by providing detailed context in the logs, which should improve the ability to identify and resolve problems. See also: #9
I added a commit with logging (and updated README.md). I verified S3, filesystem, memory and sqlite storage works here on Linux. Can you provide the logging output and OS info? |
Nevermind, I understand this feature. It only works if we use
|
The issue in your screenshot is likely due to the required SSL for Firebase in the front-end implementation. One workaround is running Excalidraw locally using a reverse-proxy setup with Caddy. Caddy can automatically generate valid, self-signed SSL certificates and install them in the browser |
Hi @PatWie , one new issue that I observed in the Room Server is: when I try to open a colab room, sometimes the people in the rooms keep increasing although only 2 of my browsers are active. Basically when I draw for sometimes (10s) and the number of people increases. |
This is unfortunately a known issue without a known root-cause: |
Hey @PatWie, I really appreciate your work and now the builds from the
dev
channel are working. 🥳But there's still some work to do until the firebase storage is being replaced completely.
One thing that still seems to be missing is the storage of blobs (images and other uploads). They don't use
firestore.googleapis.com
butfirebasestorage.googleapis.com
and those requests are not being replaced currently.I'm a DevOps guy and not a developer but I really would like to help you with bringing this forward. What is the best way to help you with this?
Thanks 😎
Christian
The text was updated successfully, but these errors were encountered: