Demo: pglite & electric-sql #7
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thank you for your contributions on this topic! Did you ever faced with the challenge of implement write-paths of electric-sql? Do you know where can I find docs, perhaps? |
No, I haven't dug that deep yet |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR demonstrates how to use pglite and electric-sql with Rails on Wasm.
Implementation notes
We include a patch for Ruby to fix the stack size issue with asyncify. It might be required to re-build all the Ruby Wasm artifacts (
rb -rf build/ rubies/) to make the patch work.We also include a custom build of the
pglite-syncpackage, because the official one doesn't allow using@electric-sql/clientv0.7.x and v0.6.x just doesn't work 🤷♂️.