-
-
Notifications
You must be signed in to change notification settings - Fork 560
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
Demo instance hit Firebase quota #68
Comments
Yeah, so RTCDataChannel would be an interesting way to do things, but it would basically be a full rewrite of the multi-user code. (Not necessarily a bad thing, but not high priority, for sure.) Entering credentials to an arbitrary Firebase instance sounds like a good short term solution. I would say, the most pertinent thing is to get some error handling in there for the case of hitting the quota limits. Although the console only logs a warning, which is worrying - hopefully there's a way to handle it! |
|
Added a visible message at least, in 1ca9cc3 |
Can you split off the firebase config to a config file, so we don't have to branch or merge when changes occur? |
@Mycah As far as I know, not without switching away from GitHub Pages (assuming you mean keeping it outside of version control) But I could do what @zezic suggested and allow you to enter your own Firebase credentials at runtime, ..well, I guess if you're cloning it locally, we could have the default Firebase config, and then a separate one that overrides it that you create, and then you can set up Firebase for running on keep in mind though, that the multi-user support was pretty garbage |
Sadly, I see messages about Firebase quota on http://jspaint.ml instance. Can we have any workaround features for keep multiuser working? Maybe, feature to enter own Firebase credentials for small session with friends? Or RTCDataChannel solution?
The text was updated successfully, but these errors were encountered: